This is precisely the scenario that the pull --complement is intended to address.
Basically, you have repository A and your friend has repository B, and he has a patch Bn that you don't want in your working repository A. Simply create another local repository of yours, called C. When you identify a patch that you don't want in A (in this case, Bn), pull it into C instead. Whenever you pull patches from A to B, just complement that against C: $ cd A $ darcs pull --complement /path/to/B ../C Any patch that is in B but not in A or C is a candidate for pulling; since Bn is in C, it is removed from the available set for pulls. -KQ On Tue, 01 May 2007 10:21:16 +0000, Joachim Breitner <[EMAIL PROTECTED]> wrote: > > New submission from Joachim Breitner <[EMAIL PROTECTED]>: > > I recently did my first experiments with darcs: A friend of mine and I hacked > on > the same code, and by giving each other access to one’s darcs repository, we > could easily exchange our new code. > > One problem I had was that my friend recorded a patch that I did not want > applied in my repository. Nothing else depended on it, so I could just say no > everytime I use “darcs pull”, but it’s still a hassle. Also, imagine that I’m > somewhere else and I suddently decide that I do want the patch? > > A similar problem would be if I created some patches that I temporarily don’t > want applied. I could branch, and then unpull them, but this is a bit too > much work. > > In both cases a “patch shelve” would be handy. A seperate storage for patches > in > my repository that are available, but not applied. I’d imagine that the “darcs > pull” command would then allow me to “pull and put on the shelf”, and not > offer > me this patch again. There would also be “put on shelf” and “get from shelf” > commands. So if anyone feels like hacking on darcs, this feature would be > appreciated. > > ---------- > messages: 1665 > nosy: EricKow, beschmi, droundy, nomeata, tommy > priority: wishlist > status: unread > title: Patch Shelf feature > > ____________________________________ > Darcs issue tracker <[EMAIL PROTECTED]> > <http://bugs.darcs.net/issue447> > ____________________________________ > _______________________________________________ > darcs-devel mailing list > [email protected] > http://lists.osuosl.org/mailman/listinfo/darcs-devel -- -- Kevin Quick quick at org after sparq
pgpDAsGXd1uWr.pgp
Description: PGP signature
_______________________________________________ darcs-devel mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-devel
