From: Thomas Rast <trast@student.ethz.ch>
To: Michael J Gruber <git@drmicha.warpmail.net>,
Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Cc: Johannes Sixt <j.sixt@viscovery.net>, <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 2/2] rev-parse --branches/--tags/--remotes=pattern
Date: Thu, 21 Jan 2010 18:27:05 +0100 [thread overview]
Message-ID: <201001211827.05847.trast@student.ethz.ch> (raw)
In-Reply-To: <4B585BED.700@drmicha.warpmail.net>
Thanks Ilari for implementing my wishes :-)
On Thursday 21 January 2010 14:51:41 Michael J Gruber wrote:
> Johannes Sixt venit, vidit, dixit 21.01.2010 13:51:
> > Works for me, thank you very much!
> >
> > Junio, kindly squash in these speeling fixes in both patches:
> >
> > sed -i 's/impiled/implied/g' `git diff HEAD^ --name-only Documentation/`
> >
>
> Also, the option descriptions are kind of staccato English right now,
> lacking a few "the" here and there. Should we fix this or simply leave
> it at that?
Maybe the --branches, --tags and --remotes could be consolidated a
bit, as in the draft patch below. If --all took a pattern, it could
be included there too, but that would probably look too weird.
diff --git i/Documentation/git-rev-parse.txt w/Documentation/git-rev-parse.txt
index 2bbb566..6fce919 100644
--- i/Documentation/git-rev-parse.txt
+++ w/Documentation/git-rev-parse.txt
@@ -104,29 +104,26 @@ OPTIONS
Show all refs found in `$GIT_DIR/refs`.
--branches[=pattern]::
- Show branch refs found in `$GIT_DIR/refs/heads`. If `pattern`
- is given, only branches matching given shell glob are shown.
- If pattern lacks '?', '*', or '[', '/*' at the end is impiled.
-
--tags[=pattern]::
- Show tag refs found in `$GIT_DIR/refs/tags`. If `pattern`
- is given, only tags matching given shell glob are shown.
- If pattern lacks '?', '*', or '[', '/*' at the end is impiled.
-
--remotes[=pattern]::
- Show tag refs found in `$GIT_DIR/refs/remotes`. If `pattern`
- is given, only remote tracking branches matching given shell glob
- are shown. If pattern lacks '?', '*', or '[', '/*' at the end is
- impiled.
+ Show all branches, tags, or remote-tracking branches,
+ respectively (i.e., refs found in `$GIT_DIR/refs/heads`,
+ `$GIT_DIR/refs/tags`, or `$GIT_DIR/refs/remotes`,
+ respectively).
++
+If a `pattern` is given, only refs matching the given shell glob are
+shown. If the pattern does not contain a globbing character (`?`,
+`\*`, or `[`), it is anchored by appending `/\*`.
+
+--glob=pattern::
+ Show all refs matching the shell glob pattern `pattern`. If
+ the pattern does not start with `refs/`, this is automatically
+ prepended. If the pattern does not contain a globbing
+ character (`?`, `\*`, or `[`), it is anchored by appending `/\*`.
--show-toplevel::
Show the absolute path of the top-level directory.
---glob=glob-pattern::
- Show refs matching shell glob pattern `glob-pattern`. If pattern
- specified lacks leading 'refs/', it is automatically prepended.
- If pattern lacks '?', '*', or '[', '/*' at the end is impiled.
-
--show-prefix::
When the command is invoked from a subdirectory, show the
path of the current directory relative to the top-level
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2010-01-21 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 9:48 [PATCH 1/2] rev-parse --glob Ilari Liusvaara
2010-01-20 9:48 ` [PATCH 2/2] rev-parse --branches/--tags/--remotes=pattern Ilari Liusvaara
2010-01-20 10:18 ` Junio C Hamano
2010-01-21 12:51 ` Johannes Sixt
2010-01-21 13:51 ` Michael J Gruber
2010-01-21 17:27 ` Thomas Rast [this message]
2010-01-21 20:09 ` Junio C Hamano
2010-01-22 0:21 ` [PATCH] Documentation: improve description of --glob=pattern and friends Thomas Rast
2010-01-22 0:51 ` Junio C Hamano
2010-01-21 17:58 ` [PATCH 2/2] rev-parse --branches/--tags/--remotes=pattern Junio C Hamano
2010-01-20 10:17 ` [PATCH 1/2] rev-parse --glob Junio C Hamano
2010-01-20 11:08 ` Ilari Liusvaara
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=201001211827.05847.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ilari.liusvaara@elisanet.fi \
--cc=j.sixt@viscovery.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.