From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] branch doc: Change `git branch <pattern>` to use `<branchname>`
Date: Thu, 23 Mar 2017 17:48:58 -0700 [thread overview]
Message-ID: <20170324004858.GE20794@aiede.mtv.corp.google.com> (raw)
In-Reply-To: <xmqq37e3brxz.fsf@gitster.mtv.corp.google.com>
Junio C Hamano wrote:
> I can go without "Do not forget ..." and everything that follows,
> though, and if we are going to do so, then
>
> --list::
> List branches. With optional <pattern>...,
> e.g. `git branch --list 'maint-*`, list only the
> branches that match the pattern(s).
>
> would be fine. I am not opposed to having an visually distinctive
> example--I just do not want to have one that is wrong without
> clearly marking it as such.
I like this one. I haven't witnessed "git branch maint-*" being a
common mistake.
For comparison, "git branch -l maint-*" does seem to be a common
mistake. It's a shame that the short-and-sweet "-l" was taken for
that purpose. Perhaps it's worth calling that out here?
--list::
--list <pattern>::
List branches. If <pattern> is specified (e.g.,
"git branch --list 'maint-*'), list only the
branches that match the pattern.
+
This should not be confused with `git branch -l <branchname>`,
which creates a branch named `<branchname>` with a reflog.
See `--create-reflog` above for details.
Thanks,
Jonathan
next prev parent reply other threads:[~2017-03-24 0:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 12:03 [PATCH] branch doc: Change `git branch <pattern>` to use `<branchname>` Ævar Arnfjörð Bjarmason
2017-03-23 17:01 ` Junio C Hamano
2017-03-23 17:44 ` Ramsay Jones
2017-03-23 19:01 ` Junio C Hamano
2017-03-23 21:07 ` Ævar Arnfjörð Bjarmason
2017-03-23 21:31 ` Junio C Hamano
2017-03-24 0:48 ` Jonathan Nieder [this message]
2017-03-24 4:56 ` [PATCH] branch doc: update description for `--list` Junio C Hamano
2017-03-24 5:00 ` Jonathan Nieder
2017-03-24 11:06 ` Ævar Arnfjörð Bjarmason
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170324004858.GE20794@aiede.mtv.corp.google.com \
--to=jrnieder@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).