On Sat, May 14, 2016 at 11:43 AM, Marko Käning <sec001+fos...@posteo.net> wrote:
> Hi devs, > > as it seems there is no demand of a “cp” command for fossil, really, as > nothing > seems to have been done about it in the last 3 years [1]. > > I guess, it’s the same issue: someone would have to implement it... > No, it’s not me either. ;) > > Anyway, still, I consider Fossil a great tool despite it lacking keeping > history > when copying files around. > 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. 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. 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'. -- ----- 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
