From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Sverre Rabbelier" <srabbelier@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Artur Skawina" <art.08.09@gmail.com>,
"Git List" <git@vger.kernel.org>
Subject: [PATCH] Documentation: explain "git branch --with"
Date: Tue, 7 Sep 2010 00:52:09 -0500 [thread overview]
Message-ID: <20100907055209.GT1182@burratino> (raw)
In-Reply-To: <7v39tmtpci.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> It was originally called --with. I wrote it to help me in the exact use
> case in this thread, and the option was naturally named --with, as the
> request I wanted to make was "Give me branches _with_ this commit, so that
> I know which ones I need to rewind before reintegrating and publishing".
>
> Somehow people wanted to see an option with a longer name, but by that
> time my fingers were well trained, so I kept "--with" but didn't bother
> advertising duplicated options.
More precisely, it is advertised by "git branch --help-all" but not
the manual or "git branch -h".
How about adding it to the man page so people can look up this option
after encountering it in the wild?
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
---
Documentation/git-branch.txt | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt
index 1940256..f479e2f 100644
--- a/Documentation/git-branch.txt
+++ b/Documentation/git-branch.txt
@@ -142,6 +142,7 @@ start-point is either a local or remote branch.
branch points to is not changed.
--contains <commit>::
+--with <commit>::
Only list branches which contain the specified commit.
--merged [<commit>]::
--
1.7.2.3
next prev parent reply other threads:[~2010-09-07 5:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 20:34 Determining commit reachability Artur Skawina
2010-09-06 3:17 ` Jeff King
2010-09-06 5:04 ` Artur Skawina
2010-09-06 6:47 ` Junio C Hamano
2010-09-06 20:45 ` Sverre Rabbelier
2010-09-06 20:53 ` Ævar Arnfjörð Bjarmason
2010-09-06 21:05 ` Sverre Rabbelier
2010-09-06 23:38 ` Junio C Hamano
2010-09-07 5:52 ` Jonathan Nieder [this message]
2010-09-07 10:51 ` [PATCH] Documentation: explain "git branch --with" Ævar Arnfjörð Bjarmason
2010-09-09 22:45 ` Junio C Hamano
2010-09-07 13:04 ` Determining commit reachability Nguyen Thai Ngoc Duy
2010-09-07 13:07 ` Nguyen Thai Ngoc Duy
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=20100907055209.GT1182@burratino \
--to=jrnieder@gmail.com \
--cc=art.08.09@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=srabbelier@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;
as well as URLs for NNTP newsgroup(s).