git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/3] git-tar-tree: documentation update
Date: Sun, 18 Jun 2006 15:06:59 +0200	[thread overview]
Message-ID: <44954FF3.9060001@lsrfire.ath.cx> (raw)
In-Reply-To: <11506282792065-git-send-email-rene.scharfe@lsrfire.ath.cx>

>  * add example on how to avoid adding a global extended pax header
>  * don't mention linux anymore, use git itself as an example instead
>  * update to v1.4.0 ;-)
>  * append missing :: to the examples

Oops, I forgot to mention this change:

> -git tar-tree HEAD | (cd /var/tmp/ && mkdir junk && tar Cxf junk -)::
> +git tar-tree HEAD junk | (cd /var/tmp/ && tar xf -)::
>  
>  	Create a tar archive that contains the contents of the
>  	latest commit on the current branch, and extracts it in
>  	`/var/tmp/junk` directory.

The new version features less typing and no more path duplication.

René

      reply	other threads:[~2006-06-18 13:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-18 10:57 [PATCH 2/3] git-tar-tree: documentation update Rene Scharfe
2006-06-18 13:06 ` Rene Scharfe [this message]

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=44954FF3.9060001@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).