On 11/1/05, Karel Gardas <[EMAIL PROTECTED]> wrote: > On Tue, 1 Nov 2005, Robert Anderson wrote: > > > Having a one-step accept/reject process would be clumsy and redundant if I > > wanted to split a patch into three parts. I'd have to reject the hunks that > > belong in the last patch twice. I'd rather fan them out in one step. > > True, but how to do this in UI-frendly manner?
Reasonable approaches seem fairly straightforward to me. Present each hunk to the user, press <return> to leave it in the current tree, or repeat the last action, which always becomes the default. Press 'a' (or 'b', etc.) to move it to tree 'a', if tree 'a' doesn't exist, create it. ctrl-k to kill the patch (undo it, or it move it to a special null tree that you intend to delete later). '!' to process all remaining hunks like the last one. ctrl-n to process all hunks in this file by the default action, and move to the next file. Something like that. That is emacs flavored but you get the idea. > > Another problem with the accept/reject process that makes it a non-starter > > IMO is that the tree you are committing never exists as a fully formed tree > > that you can build/test/etc. Factoring out into working directories allows > > you to apply your build/test process to each state of the tree independently > > before committing. > > Don't forget that in darcs you commit (record) into the working directory > repository, so you can freely record your three patches I don't understand what you mean. I don't have three patches yet. Bob _______________________________________________ Gnu-arch-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/
