On 14 May 2016, at 12:11 , Stephan Beal <sgb...@googlemail.com> wrote: > in 20+ years of using source control, i've never seen an 'cp' command (maybe > i've just overlooked it in CVS/SVN). Fossil does have an 'mv' command which > does retain history. Copying the same file to multiple places, while keeping > the history for each and every copy, seems highly questionable to me.
SVN and Mercurial have a copy command which keeps history. > consider: > > scm cp a b > > now my history looks like 'b' has existed as long as 'a' has, which would be > a bald-faced lie. Admittedly. :) > Checking out an older version, from before the copy, would presumably _not_ > want to check out 'b', but retaining its history would imply that 'b' should > indeed be retroactively applied to checkouts of any version which contains > 'a’. Well, I guess in Fossil one will simply have to leave a not in the commit message from where a specific copied file originates then. :) Greets, Marko _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
