git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Documentation: git-add: correct first example

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 8, 2010, 19:22 UTC
Message-ID
<7vsk9bmt1h.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1265650551-32664-1-git-send-email-gbacon@dbresearch.net>
Greg Bacon <gbacon@dbresearch.net> writes:
> The first example for git-add covers recursive adding of patterns but
> contains an extra backslash.
Correct.  
Show 15 quoted lines
> Signed-off-by: Greg Bacon <gbacon@dbresearch.net>
> ---
>  Documentation/git-add.txt |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt
> index f74fcf3..93e8f57 100644
> --- a/Documentation/git-add.txt
> +++ b/Documentation/git-add.txt
> @@ -149,11 +149,12 @@ those in info/exclude.  See linkgit:gitrepository-layout[5].
>  EXAMPLES
>  --------
>  
> -* Adds content from all `\*.txt` files under `Documentation` directory
> +* Adds content from all `*.txt` files under `Documentation` directory
For this, both
    http://www.kernel.org/pub/software/scm/git/docs/git-add.html
and output from
    git help add
in my local build seem to be rendered correctly by AsciiDoc.
>  and its subdirectories:
>  +
>  ------------
> -$ git add Documentation/\\*.txt
This indeed results in double-backslash in the output.
> +$ git add Documentation/\*.txt
and this seems to fix it.
Thanks.
Previous: Greg BaconNext: Junio C Hamano
Message 2 of 3 in “Documentation: git-add: correct first example”
  1. Documentation: git-add: correct first exampleGreg Bacon, Feb 8, 2010
  2. Junio C HamanoFeb 8, 2010
  3. Junio C HamanoFeb 8, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.