git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es>,
	git@vger.kernel.org
Subject: Re: [PATCH] rebase -i: inform the user they can re-order commits
Date: Fri, 16 Mar 2012 06:36:04 -0700 (PDT)	[thread overview]
Message-ID: <m3pqccllbt.fsf@localhost.localdomain> (raw)
In-Reply-To: <vpq7gyklq3i.fsf@bauges.imag.fr>

Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es> writes:
> 
> > >   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.
> 
> Perfect. "are applied" says more than my "in history", since rebase -i
> is all about various ways to apply commits.

Nitpick: shouldn't it be s/the commits/commits/

    You can re-order the lines to change the order commits are applied.

-- 
Jakub Narebski

  reply	other threads:[~2012-03-16 13:36 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
2012-03-16 11:53     ` Matthieu Moy
2012-03-16 13:36       ` Jakub Narebski [this message]
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=m3pqccllbt.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=nelsonjesus.benitez@seap.minhap.es \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).