git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Dickson <paul@permanentmail.com>
To: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Cc: pasky@ucw.cz, git@vger.kernel.org
Subject: Re: [PATCH] Add archive-tree, a cpio archive creator
Date: Mon, 25 Apr 2005 15:30:11 -0700	[thread overview]
Message-ID: <20050425153011.34c93b38.paul@permanentmail.com> (raw)
In-Reply-To: <20050424014346.GA23083@lsrfire.ath.cx>

On Sun, 24 Apr 2005 03:43:46 +0200, Rene Scharfe wrote:

> This patch adds archive-tree, a program to create a cpio archive of all
> files referenced by a given tree or commit object.  Why cpio and not
> e.g., tar?  The cpio format I chose (GNU cpio calls it "odc") is dead
> simple compared to any tar variant.  I was simply being lazy. :-P

Use the "newc" format.  The "odc" will generate a lot of errors on a
large filesystem (which I discovered this past weekend).

	-Paul


  reply	other threads:[~2005-04-25 22:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-24  1:43 [PATCH] Add archive-tree, a cpio archive creator Rene Scharfe
2005-04-25 22:30 ` Paul Dickson [this message]
2005-04-26 14:42   ` Rene Scharfe

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=20050425153011.34c93b38.paul@permanentmail.com \
    --to=paul@permanentmail.com \
    --cc=git@vger.kernel.org \
    --cc=pasky@ucw.cz \
    --cc=rene.scharfe@lsrfire.ath.cx \
    /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).