>This depends.  The simple case is if there are no patches which affect
>both the private files and the public ones.  In that case, you can just
>obliterate the relevant patches.

Ah, that makes sense. Any idea how I could find those patches easily?

>The solution would probably be to generate a Unix diff representing
>the public file changes in the patches you want to get rid of,
>obliterate the patches, apply the diff and then record a new patch.

Right. That's been the solution for so many problems for such a long time...

I'd suggest an option to the "remove" command to delete a file from all 
patches. Or a command to "split" a repository in N (including splitting all 
patches), so I could keep the history of the private files in a separate repo 
too.

BTW, can I mutate the contents of a patch file?



-- Dan






_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users

Reply via email to