From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-show-ref: fix escaping in asciidoc source
Date: Tue, 15 Nov 2011 15:11:52 +0100 [thread overview]
Message-ID: <4EC27328.3070309@alum.mit.edu> (raw)
In-Reply-To: <1319050336-24717-1-git-send-email-mhagger@alum.mit.edu>
Junio,
Did this one fall through the cracks? I don't see it in your tree.
Michael
On 10/19/2011 08:52 PM, mhagger@alum.mit.edu wrote:
> From: Michael Haggerty <mhagger@alum.mit.edu>
>
> One of the "^" characters was not coming through in the man page.
>
> Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
> ---
> Documentation/git-show-ref.txt | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/git-show-ref.txt b/Documentation/git-show-ref.txt
> index 3c45895..87f358d 100644
> --- a/Documentation/git-show-ref.txt
> +++ b/Documentation/git-show-ref.txt
> @@ -44,7 +44,7 @@ OPTIONS
> -d::
> --dereference::
>
> - Dereference tags into object IDs as well. They will be shown with "^{}"
> + Dereference tags into object IDs as well. They will be shown with "{caret}\{\}"
> appended.
>
> -s::
> @@ -75,7 +75,7 @@ OPTIONS
> Make 'git show-ref' act as a filter that reads refs from stdin of the
> form "^(?:<anything>\s)?<refname>(?:{backslash}{caret}\{\})?$"
> and performs the following actions on each:
> - (1) strip "^{}" at the end of line if any;
> + (1) strip "{caret}\{\}" at the end of line if any;
> (2) ignore if pattern is provided and does not head-match refname;
> (3) warn if refname is not a well-formed refname and skip;
> (4) ignore if refname is a ref that exists in the local repository;
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2011-11-15 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 18:52 [PATCH] git-show-ref: fix escaping in asciidoc source mhagger
2011-10-19 19:43 ` Junio C Hamano
2011-11-15 14:11 ` Michael Haggerty [this message]
2011-11-15 19:16 ` Junio C Hamano
2011-11-16 5:52 ` Michael Haggerty
2011-11-16 11:54 ` Michael Haggerty
2011-11-16 13:08 ` Thomas Rast
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=4EC27328.3070309@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--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.
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).