One more thing: make sure you keep a backup of your original repository before doing any manual removals of patch files. Then be sure to run darcs check when you're done to make sure that your repo is in a consistent state before proceeding to make further changes.
On 10/28/06, Nimrod A. Abing <[EMAIL PROTECTED]> wrote:
If those patches are not dependencies of other patches that you wish to make public then you can just uncompress your patches files and grep for that patches that you want to remove, then you rm them. At least that's what I did the last time it happened to me. I comitted a patch that revealed username and password. There were already 30 patches on top of this but luckily, no other patch depended on this. If the patch you want to remove is a dependency of other patches, then get ready to tear your hair out :) I think theres a patch dependency graphing program posted in the mailing list before. I forget what its called or where to get it but it helped a lot to track dependencies in my case. On 10/28/06, Dan <[EMAIL PROTECTED]> wrote: > Hi all, > > I have a darcs repo that was until now private, and I want to make it public. Unfortunately the repo history contains some old files (and their history) that cannot be made public. How can I create a cleansed public repo? Can I just run "darcs remove" and then remove the patch files that refer to the offending files? > > Sure, this could be achieved by running a number of patches in reverse and creating a new repo, but I hope there's an easier way. > > -- Dan > > > > > > _______________________________________________ > darcs-users mailing list > [email protected] > http://www.abridgegame.org/mailman/listinfo/darcs-users > -- _nimrod_a_abing_ [?] http://abing.gotdns.com
-- _nimrod_a_abing_ [?] http://abing.gotdns.com _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
