Hi Aaron, Is there any chance you would like to try your hand at helping Lyle out? It may be good research for whether we need a darcs transplant command or not.
Thanks! (P.S. we also need to rule out the more basic stuff, for example, if the patches in question only touch LICENSE.txt, then it's just a matter of cherry picking --match 'touch LICENSE.txt') On Tue, Feb 10, 2009 at 11:25:14 -0800, Lyle Kopnicky wrote: > Hi folks, > > I have a basic working knowledge of Darcs, but am not familiar with many of > the advanced commands. I recently discovered that back in January, I had > accidentally overwritten my project's LICENSE.txt file with a binary > (apparently a distribution tarball). It was recorded as part of a patch > along with other useful changes. I was able to fix the file by recreating it > and recording the change. But now I have two giant patches in my repository: > one to add the binary (along with other changes) and another to remove it. > Furthermore, I have a backup of my repository on patch-tag.com that also has > these patches. > > What's the safest and most straightforward way to purge these copies of the > binary from my history? I'm thinking something along the lines of: figuring > out what other changes were in the first patch that I want to keep, and > storing that in a diff; obliterating the patches from the repository; > reapplying the diff and recording that. Of course there's a risk that later > patches depended on the one I obliterated, which could make the repository > inconsistent. > > Any sage wisdom would be appreciated. > > Thanks, > Lyle > _______________________________________________ > darcs-users mailing list > [email protected] > http://lists.osuosl.org/mailman/listinfo/darcs-users -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
