From: Lea Wiemann <lewiemann@gmail.com>
To: git@vger.kernel.org
Cc: Lea Wiemann <lewiemann@gmail.com>, Lea Wiemann <LeWiemann@gmail.com>
Subject: [PATCH v2] git-for-each-ref.txt: minor improvements
Date: Thu, 5 Jun 2008 15:38:34 +0200 [thread overview]
Message-ID: <1212673114-15751-1-git-send-email-LeWiemann@gmail.com> (raw)
In-Reply-To: <1212664752-12160-1-git-send-email-LeWiemann@gmail.com>
From: Lea Wiemann <lewiemann@gmail.com>
Rewrapped synopsis and removed wrong asterisk behind --count option;
clarified --sort=<key> description for multiple keys; documented that
for-each-ref supports not only glob patterns but also prefixes like
"refs/heads" as patterns.
Signed-off-by: Lea Wiemann <LeWiemann@gmail.com>
---
Added more fixes/improvements since v1.
Documentation/git-for-each-ref.txt | 14 +++++++-------
1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt
index f1f90cc..4ffc65f 100644
--- a/Documentation/git-for-each-ref.txt
+++ b/Documentation/git-for-each-ref.txt
@@ -8,8 +8,7 @@ git-for-each-ref - Output information on each ref
SYNOPSIS
--------
[verse]
-'git-for-each-ref' [--count=<count>]\*
- [--shell|--perl|--python|--tcl]
+'git-for-each-ref' [--count=<count>] [--shell|--perl|--python|--tcl]
[--sort=<key>]\* [--format=<format>] [<pattern>]
DESCRIPTION
@@ -32,8 +31,9 @@ OPTIONS
<key>::
A field name to sort on. Prefix `-` to sort in
descending order of the value. When unspecified,
- `refname` is used. More than one sort keys can be
- given.
+ `refname` is used. You may use the --sort=<key> option
+ multiple times, in which case the last key becomes the primary
+ key.
<format>::
A string that interpolates `%(fieldname)` from the
@@ -48,9 +48,9 @@ OPTIONS
`%09` to `\t` (TAB) and `%0a` to `\n` (LF).
<pattern>::
- If given, the name of the ref is matched against this
- using fnmatch(3). Refs that do not match the pattern
- are not shown.
+ If given, only refs are shown that match againt the pattern
+ either using fnmatch(3) or literally, in the latter case up to
+ a slash or entirely.
--shell, --perl, --python, --tcl::
If given, strings that substitute `%(fieldname)`
--
1.5.6.rc1.9.g69bbf.dirty
next prev parent reply other threads:[~2008-06-05 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 11:19 [PATCH] git-for-each-ref.txt: fix description of <pattern> Lea Wiemann
2008-06-05 13:38 ` Lea Wiemann [this message]
2008-06-05 18:40 ` [PATCH v3] git-for-each-ref.txt: minor improvements Lea Wiemann
2008-06-05 18:58 ` Junio C Hamano
2008-06-05 20:54 ` [PATCH] git-for-each-ref.txt: minor fixes Lea Wiemann
2008-06-05 21:01 ` [PATCH v5] git-for-each-ref.txt: minor improvements Lea Wiemann
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=1212673114-15751-1-git-send-email-LeWiemann@gmail.com \
--to=lewiemann@gmail.com \
--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).