Hi Ashley, Ashley's use case: am> Currently we use a shared Dropbox folder and do this (2-3 times per week if am> there are 3 of us, massively more often on the rare occasion we had 4 people am> at the same time): am> am> * B records patch "WIP - UNRECORD" am> * C pulls "WIP - UNRECORD" am> * C unrecords "WIP - UNRECORD" am> * B obliterates "WIP - UNRECORD" On Mon, Jul 19, 2010 at 18:33:04 -0400, Max Battcher wrote: mb> Right now, it seems to me that Ashley Moran's use case could mostly be mb> handled by normal patch exchange and amend-record to move from mb> work-in-progress to "releasable" patch states.
Max has a point there, Ashley. If you're going to work this way (obliterating patches that others have pulled) why not just record a bunch of "WIP" patches and when you're ready to save them, do something like darcs unrecord --match 'name ^WIP'? darcs record Thanks, -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> For a faster response, please try +44 (0)1273 64 2905.
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
