On Wednesday 14 January 2009, Junio C Hamano <gitster@xxxxxxxxx> wrote about 'Re: [RFC PATCH] Make the rebase edit mode really end up in an edit state': >Anders Melchiorsen <mail@xxxxxxxxxxxxxxxx> writes: >> I always have a hard time figuring out what to do during an >> interactive rebase. Recently, it dawned on me that the reason is that >> I have to do different things: one thing when editing on purpose, and >> a different thing when resolving a conflict. >> >> With this change, I propose to make the UI more uniform. I think that >> the new way is more intuitive, too, if you will agree that a Git UI >> can be intuitive. >> >> I expect this to not be acceptable due to compatibility concerns. > >We may need a version bump to 1.7.0 to update the UI for this command, > but please do test rigorously to build a stronger case for a saner UI. Instead of changing the meaning of edit, how about introducing a "replace" command? -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@xxxxxxxxxxxxxxxxx ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.
