From: "Philip Jägenstedt" <philip@foolip.org>
To: git@vger.kernel.org
Subject: Re: [PATCH] remote: align set-branches builtin usage and documentation
Date: Sat, 18 Feb 2012 14:11:44 +0100 [thread overview]
Message-ID: <CAKHWUkY2ZNniJmhheHdxj4dzBLtY-+Pn4teAm2WE+0eTXYMYvg@mail.gmail.com> (raw)
In-Reply-To: <1329563867-13283-1-git-send-email-philip@foolip.org>
On Sat, Feb 18, 2012 at 12:17, Philip Jägenstedt
<philip.jagenstedt@gmail.com> wrote:
> The order of [--add] <name> <branch>... was inconsistent
> between builtin remote usage messages and git-remote.txt.
To clarify, it's the order of "git remote set-branches" that is
inconsistent with the two instances the patch touches:
usage: git remote set-branches <name> <branch>...
or: git remote set-branches --add <name> <branch>...
--
Philip Jägenstedt
prev parent reply other threads:[~2012-02-18 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-18 11:17 [PATCH] remote: align set-branches builtin usage and documentation Philip Jägenstedt
2012-02-18 13:11 ` Philip Jägenstedt [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=CAKHWUkY2ZNniJmhheHdxj4dzBLtY-+Pn4teAm2WE+0eTXYMYvg@mail.gmail.com \
--to=philip@foolip.org \
--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 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).