Git development
 help / color / mirror / Atom feed
From: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>,
	git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>,
	Drew Northup <drew.northup@maine.edu>
Subject: Re: [PATCH v2] git-rebase.txt: clarify that --abort checks out <branch>
Date: Sun, 10 Jul 2011 14:07:45 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1107100841400.2491@debian> (raw)
In-Reply-To: <7vzkkog3ia.fsf@alter.siamese.dyndns.org>

Hi Junio,

On Fri, 8 Jul 2011, Junio C Hamano wrote:

> Martin von Zweigbergk <martin.von.zweigbergk@gmail.com> writes:
> 
> >  --skip::
> >  	Restart the rebasing process by skipping the current patch.
> > diff --git a/git-rebase.sh b/git-rebase.sh
> > index d7855ea..f2d4c72 100755
> > --- a/git-rebase.sh
> > +++ b/git-rebase.sh
> > @@ -58,7 +58,7 @@ ignore-whitespace! passed to 'git apply'
> >  C=!                passed to 'git apply'
> >   Actions:
> >  continue!          continue rebasing process
> > -abort!             abort rebasing process and restore original branch
> > +abort!             abort rebasing process and reset HEAD to <branch>
> >  skip!              skip current patch and continue rebasing process
> >  "
> 
> I don't think it is quite right to use placeholder notation here, unless
> you are talking about "git rebase --abort <branch>", and you are of course
> not in this case. Perhaps
> 
> 	abort and check out the original branch
> 
> might be slightly better. I dunno.

Good point. I tried to find something that would fit in 80 characters
and still not use the term "check out", but I agree that using the
placeholder notation was a bad idea. I would be happy to change to
your proposed text. Drew, I hope you don't mind.

> As the user knows these help text are all about "rebase", I do not think
> it is worth repeating "rebasing process" over and over again.

I was thinking about changing "rebasing process" to "rebase", but
removing it completely is probably good idea.

Patch coming up.

  reply	other threads:[~2011-07-10 18:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02  2:38 [PATCH 2/2] git-rebase.txt: clarify that --abort checks out <branch> Martin von Zweigbergk
2011-07-05 21:43 ` Drew Northup
2011-07-06  2:19   ` Martin von Zweigbergk
2011-07-06  2:52     ` Jonathan Nieder
2011-07-06 13:25       ` Drew Northup
2011-07-08  2:27 ` [PATCH v2] " Martin von Zweigbergk
2011-07-08 16:07   ` Junio C Hamano
2011-07-10 18:07     ` Martin von Zweigbergk [this message]
2011-07-10 18:31   ` [PATCH v3] " Martin von Zweigbergk
2011-07-14  3:47     ` [PATCH v4] rebase: clarify "restore the original branch" Martin von Zweigbergk

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=alpine.DEB.2.00.1107100841400.2491@debian \
    --to=martin.von.zweigbergk@gmail.com \
    --cc=drew.northup@maine.edu \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    /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