On Jul 22, 2010, at 2:02 pm, Eric Kow wrote: > 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
Hi Eric, Max Sorry for the delay replying. Max is correct, that this can be done using existing features in Darcs. It's a *lot* easier now all the repos are on Dropbox - doing this workflow with patchbundle files is painful. But it's something that come up often enough that I started to wish that transferring WIP could be done in one move. It hasn't been an issue lately, as I've only had one concurrent pair working on the code (me and someone else). It may only be beneficial to teams that do rapid pair switching, and maybe also only if the team is (partially) distributed... which I imagine isn't a huge proportion of darcs users. Cheers Ash -- http://www.patchspace.co.uk/ http://www.linkedin.com/in/ashleymoran _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
