On Oct 8, 2009, at 6:42 AM, Dan Drake wrote: > On Thu, 08 Oct 2009 at 06:11AM -0700, Nathann Cohen wrote: >> The thing is that is it a pretty hard patch to send... If someone is >> sending a patch for this file while another patch is removing this >> file and creating three others... If that's how HG works ;-) > > Mercurial should support this. If the big file is copied to the three > new files (using "hg copy") and then the correct bits removed from > each > file, the resulting patch (if exported in the right format) will > convey > this information. > > Then if another patch comes along that refers to the original big > file, > I think Mercurial can figure out where it should look.
That is *if* git-style patches or bundles are used. Normal unified diffs have no concept of a move, only a delete and add. - Robert --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
