From: Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] rebase -i: inform the user they can re-order commits
Date: Fri, 16 Mar 2012 12:34:27 +0100 [thread overview]
Message-ID: <4F632543.50402@seap.minhap.es> (raw)
In-Reply-To: <vpqlin0n8w5.fsf@bauges.imag.fr>
On 03/16/2012 11:21 AM, Matthieu Moy wrote:
> Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es> writes:
>
>> +# You can re-order the commit lines to affect the order on which
>> +# the commits will be applied.
>
> That's probably the main use of "rebase -i", so it deserves a mention,
> yes.
>
> Maybe shorten it to one line like
>
> You can re-order the lines to change the order of commits in history.
I like it but the word 'history' seems a bit too technical for me, and may
scare the normal user,, what about:
You can re-order the lines to change the order the commits are applied.
> (BTW, is it not 'order in which', not '_on_ which'?)
>
May be, non-native english speaker here..
next prev parent reply other threads:[~2012-03-16 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 11:13 [PATCH] rebase -i: inform the user they can re-order commits Nelson Benitez Leon
2012-03-16 10:21 ` Matthieu Moy
2012-03-16 11:34 ` Nelson Benitez Leon [this message]
2012-03-16 11:53 ` Matthieu Moy
2012-03-16 13:36 ` Jakub Narebski
2012-03-16 12:17 ` Junio C Hamano
2012-03-16 15:07 ` Nelson Benitez Leon
2012-03-16 14:12 ` Matthieu Moy
2012-03-16 14:26 ` Junio C Hamano
2012-03-16 14:36 ` Matthieu Moy
2012-03-16 14:46 ` Junio C Hamano
2012-03-16 14:39 ` Junio C Hamano
2012-03-20 23:07 ` Junio C Hamano
2012-03-21 8:25 ` Matthieu Moy
2012-03-21 10:45 ` Philip Oakley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F632543.50402@seap.minhap.es \
--to=nelsonjesus.benitez@seap.minhap.es \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.