[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    Re: [RFC PATCH] Make the rebase edit mode really end up in an edit state
From:       Wincent Colaiuta <win () wincent ! com>
Date:       2009-01-16 14:28:25
Message-ID: 22A54F3C-DC15-4589-B796-D0E7032EC515 () wincent ! com
[Download RAW message or body]

El 16/1/2009, a las 14:27, SZEDER Gábor escribió:

> On Fri, Jan 16, 2009 at 01:57:57PM +0100, Johannes Schindelin wrote:
>> Hi,
>>
>> On Fri, 16 Jan 2009, SZEDER Gábor wrote:
>>
>>> On Fri, Jan 16, 2009 at 11:58:06AM +0100, Johan Herland wrote:
>>>
>>>> "rephrase"?
>>>
>>> This is the first one that I found acceptable.
>>
>> I assume you missed
>> http://article.gmane.org/gmane.comp.version-control.git/105783 in  
>> all that
>> bikeshedding?
>
> Yes, I indeed missed that.  And still think that 'rephrase' is best
> among all the suggestions for this "edit just the commit message"
> thing.  ('editmsg' conflicts; 'amend', 'modify', and  'correct' are
> not obvious enough (they don't clearly indicate what will be
> modified); and I'm not sure about 'redact', but I don't really like it
> because I had to look it up in the dictionary first).

Two more colors for consideration:

   - "msg"/"msgedit"/"message" or similar
   - "reword"

I agree with Gábor that options like "modify" aren't clear because  
there's nothing in them that suggests that they're intended to operate  
on the commit _message_.

Wincent

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]