On Thu, Jul 15, 2010 at 17:11:52 +0100, Ashley Moran wrote: > * Three people, A, B and C, are working on a problem > * A and B pair on B's machine > * A and B end with WIP in B's repo > * A wants to pair with C on C's machine > * B has to transfer WIP to C's repo... how?
... > What we'd really like to do is: > > repo-a> darcs stash ../repo-b So hopefully without being too formalist about it, we can think of there being a certain number of desiderata: * save work in progress (WIP) without needing to invent a name for it * save WIP without adding to patch history * recover WIP * save multiple WIP (I recall being able to address stashes when I was trying to learn more Git, something like git unstash @4) * resist changes to repo history (Petr was talking about minimal contexts in stashes) And now you've introduced a new one: * stash against some other repository Interesting. So what would the whole workflow look like? Where is the stash saved? How does one perform an unstash? What does it meant to stash against another repository? Do we care about the contents of the other repository's working directory, or do we stash changes against their pristine (with patch commutation to make this work nicely). Lots of little tiny details to sort out for the idea of conveniently WIP. Of course, I hope this sort of questioning doesn't paralyse us. I don't mean that you need to get all the details sorted out before you embark on any endeavour; that would be silly. I guess I'm just saying that there's a little bit of a top-down aspect to UI design (I say in total ignorance), and that any effort we put into thinking about how the whole system/workflow fits together will pay off (sorry, just banging the old drum again) -- 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 [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
