From: Junio C Hamano <gitster@pobox.com>
To: "W. Trevor King" <wking@tremily.us>
Cc: Git <git@vger.kernel.org>, Thomas Rast <trast@student.ethz.ch>
Subject: Re: [PATCH v2] Documentation/githooks: Explain pre-rebase parameters
Date: Sun, 24 Feb 2013 00:13:25 -0800 [thread overview]
Message-ID: <7v621i6sey.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130223213513.GF1361@odin.tremily.us> (W. Trevor King's message of "Sat, 23 Feb 2013 16:35:13 -0500")
"W. Trevor King" <wking@tremily.us> writes:
> On Sat, Feb 23, 2013 at 01:21:59PM -0800, Junio C Hamano wrote:
>> "W. Trevor King" <wking@tremily.us> writes:
>>
>> > +This hook is called by 'git rebase' and can be used to prevent a
>> > +branch from getting rebased. The hook takes two parameters: the
>> > +upstream the series was forked from and the branch being rebased. The
>> > +second parameter will be missing when rebasing the current branch.
>>
>> takes one or two parameters?
>>
>> Other than that, looks good to me, but it took me two readings to
>> notice where these two parameters are described. I have a feeling
>> that a comma s/forked from and/forked from, and/; might make them a
>> bit more spottable, but others may have better suggestions to make
>> them stand out more.
>
> How about:
>
> The hook may be called with one or two parameters. The first
> parameter is the upstream from which the series was forked. The
> second parameter is the branch being rebased, and is not set when
> rebasing the current branch.
Much nicer. Thanks.
prev parent reply other threads:[~2013-02-24 8:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 11:03 [PATCH] Documentation/githooks: Explain pre-rebase parameters W. Trevor King
2013-02-19 13:17 ` Thomas Rast
2013-02-19 13:23 ` W. Trevor King
2013-02-19 17:05 ` Junio C Hamano
2013-02-19 19:08 ` Junio C Hamano
2013-02-20 16:36 ` W. Trevor King
2013-02-20 17:23 ` Junio C Hamano
2013-02-23 15:27 ` [PATCH v2] " W. Trevor King
2013-02-23 21:21 ` Junio C Hamano
2013-02-23 21:35 ` W. Trevor King
2013-02-24 8:13 ` Junio C Hamano [this message]
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=7v621i6sey.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
--cc=wking@tremily.us \
/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).