On Thu, Nov 29, 2007 at 06:13:23PM -0800, Ben Coburn wrote: > > On Nov 29, 2007, at 14:14, Nathan Gray wrote: > > Is it possible to create a tag by listing the patches that should be > > included, while leaving out other patches in the repository? Though I > > still have to figure out which patches I need and which I do not. > > Yes, I wrote some code to do this for special repository usage > semantics a few months ago. Here's some ideas on how to do this.... > > 1) darcs only > Create a new blank repository. Pull in only the patches you want to > tag. Create a tag. Send and apply the tag back to the full > repository. Remove the temporary repository used to create the tag. > Note: This will probably be way too slow for such a large number of > patches.
I've tried doing this in the past. As you note, it is slow. > 2) forge the tag > Use darcs changes with XML output to gather information on the > patches you want in your tag. Forge a fake output file from darcs > send with a tag listing all the patches you want to tag. Apply the > forged tag to the full repository. This sounds like it might work. I'll give this a try. > Note for both approaches: I think darcs optimize --reorder-patches > will commute the tags into the proper dependency location. This is > probably a good idea once you have got the tags into the full > repository. Sounds like a good idea. -kolibrie _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
