On Sat, May 14, 2016 at 12:25 PM, Marko Käning <sec001+fos...@posteo.net> wrote:
> 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. > But in svn, now that i think about it, cp is, in practice, only used for branching. i've never seen it used to copy something within the same tree. > > 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. :) > That would require a backwards-incompatible change to the manifest format, which would bring with it a lot of pain for a feature which seems to be only rarely useful (and never critical). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
