darcs-style cherry-picking of changes to commit ?

[Jan Hudec]

On Tue, Dec 06, 2005 at 18:38:10 +1100, Martin Pool wrote:
> On  2 Dec 2005, Michael Ellerman <michael at ellerman.id.au> wrote:
> > On Fri, 2 Dec 2005 19:57, Simon Michael wrote:
> > > Good evening all.. I'm a happy darcs user, checking out bzr which also
> > > looks great. Thanks for creating it.
> > 
> > I was also a fan of darcs hunk-selection at commit behaviour, and originally I 
> > was hoping to add something similar to bzr. (it's still a possibility)
> > 
> > However I've decided now that darcs' behaviour actually encourages bad 
> > practice, in that it makes it very easy to create revisions that never 
> > existed in your working tree. This is a bad idea because it means you end up 
> > with revisions in history that were never built or tested.
> 
> I agree that it's possible to use it in a bad way.  But there is a way
> to mitigate it.  That is: let the user choose the hunks to be committed,
> and build an in-memory tree describing what they chose.  Export that to
> a temporary directory, and run a configured selftest command in there;
> if the test fails then show the error and disallow the commit.

Why? When the user selects hunks to commit, shelve inverse selection,
run the pre-commit hooks, commit and unshelve.

-- 
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051206/06c4d6d7/attachment.pgp