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

Re: [PATCH 2/2] Be consistent in switch usage for tar

From
APAlexander Potashev <aspotashev@gmail.com>
Date
Jan 5, 2009, 18:19 UTC
Message-ID
<20090105181950.GA5403@myhost>
In-Reply-To
<1231169137-32653-3-git-send-email-henrik@austad.us>
On 16:25 Mon 05 Jan     , henrik@austad.us wrote:
> From: Henrik Austad <henrik@austad.us>
> 
> tar handles switches with and witouth preceding '-', but the documentation should be
s/witouth/without
Show 17 quoted lines
> consistent nonetheless.
> 
> Signed-off-by: Henrik Austad <henrik@austad.us>
> ---
>  Documentation/user-manual.txt |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
> index 5242a7e..19f571a 100644
> --- a/Documentation/user-manual.txt
> +++ b/Documentation/user-manual.txt
> @@ -1009,7 +1009,7 @@ $ git init
>  If you have some initial content (say, a tarball):
>  
>  -------------------------------------------------
> -$ tar -xzvf project.tar.gz
> +$ tar xzvf project.tar.gz
Btw, tar manpage uses dashed options in usage examples:
	tar -xvf foo.tar
		verbosely extract foo.tar
	...
Show 5 quoted lines
>  $ cd project
>  $ git init
>  $ git add . # include everything below ./ in the first commit:
> -- 
> 1.6.1.36.g8430e
Previous: henrik@austad.usNext: Junio C Hamano
Message 4 of 5 in “Consistency patches for Documentation/”
  1. henrik@austad.usJan 5, 2009
  2. 1/2 Use capitalized names where appropriatehenrik@austad.us, Jan 5, 2009
  3. 2/2 Be consistent in switch usage for tarhenrik@austad.us, Jan 5, 2009
  4. Alexander PotashevJan 5, 2009
  5. Junio C HamanoJan 6, 2009

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.