git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Alexei Sholik <alcosholik@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Documentation: remove redundant colons in git-for-each-ref.txt
Date: Wed, 09 Mar 2011 08:55:37 +0100	[thread overview]
Message-ID: <4D773279.4020709@drmicha.warpmail.net> (raw)
In-Reply-To: <1299590170-30799-2-git-send-email-alcosholik@gmail.com>

Alexei Sholik venit, vidit, dixit 08.03.2011 14:16:
> Signed-off-by: Alexei Sholik <alcosholik@gmail.com>
> ---
>  Documentation/git-for-each-ref.txt |    6 +++---
>  1 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt
> index fac1cf5..bffb5d2 100644
> --- a/Documentation/git-for-each-ref.txt
> +++ b/Documentation/git-for-each-ref.txt
> @@ -123,7 +123,7 @@ EXAMPLES
>  --------
>  
>  An example directly producing formatted text.  Show the most recent
> -3 tagged commits::
> +3 tagged commits:
>  
>  ------------
>  #!/bin/sh
> @@ -140,7 +140,7 @@ Ref: %(*refname)
>  
>  
>  A simple example showing the use of shell eval on the output,
> -demonstrating the use of --shell.  List the prefixes of all heads::
> +demonstrating the use of --shell.  List the prefixes of all heads:
>  ------------
>  #!/bin/sh
>  
> @@ -154,7 +154,7 @@ done
>  
>  
>  A bit more elaborate report on tags, demonstrating that the format
> -may be an entire script::
> +may be an entire script:
>  ------------
>  #!/bin/sh
>  

Maybe those were meant to be items in a labelled list, but asciidoc
doesn't seem to recognize the "::" as such here, so I think this change
is fine.

Michael

  reply	other threads:[~2011-03-09  7:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 13:16 [PATCH 0/2] A couple of tweaks in git-for-each-ref.txt Alexei Sholik
2011-03-08 13:16 ` [PATCH 1/2] Documentation: remove redundant colons " Alexei Sholik
2011-03-09  7:55   ` Michael J Gruber [this message]
2011-03-08 13:16 ` [PATCH 2/2] Add Author and Documentation sections to git-for-each-ref.txt Alexei Sholik
2011-03-09  8:08   ` Michael J Gruber
2011-03-09 12:14     ` Alexei Sholik
2011-03-17 14:20       ` Will Palmer
2011-03-17 19:34         ` Jeff King
2011-03-17 19:51           ` Alexei Sholik
2011-03-17 19:54             ` Jeff King
2011-03-17 20:10               ` Alexei Sholik
2011-03-09 20:17     ` Junio C Hamano
2011-03-10 22:37       ` Jeff King
2011-03-10 23:09         ` Junio C Hamano
2011-03-11  6:20           ` Jeff King
2011-03-11  8:09             ` Junio C Hamano
2011-03-12  9:52         ` Alexei Sholik
2011-03-13  3:02           ` Jeff King
2011-03-13  6:34             ` Junio C Hamano
2011-03-13  6:47               ` Jeff King
2011-03-13  7:33                 ` Junio C Hamano
2011-03-13 13:27                   ` Michael J Gruber
2011-03-17  6:59                   ` Jeff King
2011-03-09 19:54 ` [PATCH 0/2] A couple of tweaks in git-for-each-ref.txt 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=4D773279.4020709@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=alcosholik@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).