git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent van Ravesteijn <vfr@lyx.org>
To: git@vger.kernel.org
Cc: trast@inf.ethz.ch, gitster@pobox.com,
	Vincent van Ravesteijn <vfr@lyx.org>
Subject: [PATCHv2 2/3] Documentation/git-branch: fix a typo
Date: Tue,  6 Mar 2012 10:32:44 +0100	[thread overview]
Message-ID: <1331026365-7044-2-git-send-email-user@vincent-VirtualBox> (raw)
In-Reply-To: <1331026365-7044-1-git-send-email-user@vincent-VirtualBox>

From: Vincent van Ravesteijn <vfr@lyx.org>

Fix a typo by replacing 'tag' with 'branch'.

Signed-off-by: Vincent van Ravesteijn <vfr@lyx.org>
---
 Documentation/git-branch.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt
index d3a923a..cfceac5 100644
--- a/Documentation/git-branch.txt
+++ b/Documentation/git-branch.txt
@@ -25,7 +25,7 @@ branches to be listed, and option `-a` shows both. This list mode is also
 activated by the `--list` option (see below).
 <pattern> restricts the output to matching branches, the pattern is a shell
 wildcard (i.e., matched using fnmatch(3)).
-Multiple patterns may be given; if any of them matches, the tag is shown.
+Multiple patterns may be given; if any of them matches, the branch is shown.
 
 With `--contains`, shows only the branches that contain the named commit
 (in other words, the branches whose tip commits are descendants of the
-- 
1.7.5.4

  reply	other threads:[~2012-03-06  9:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06  8:51 [PATCH] Documentation update for 'git branch' vfr
2012-03-06  9:00 ` Thomas Rast
2012-03-06  9:32 ` [PATCHv2 1/3] Documentation/git-branch: cleanups Vincent van Ravesteijn
2012-03-06  9:32   ` Vincent van Ravesteijn [this message]
2012-03-06  9:32   ` [PATCHv2 3/3] Documentation/git-branch: add default for --contains Vincent van Ravesteijn
2012-03-06 19:43   ` [PATCHv2 1/3] Documentation/git-branch: cleanups Junio C Hamano

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=1331026365-7044-2-git-send-email-user@vincent-VirtualBox \
    --to=vfr@lyx.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=trast@inf.ethz.ch \
    /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).