From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Paul Dickson <paul@permanentmail.com>
Cc: pasky@ucw.cz, git@vger.kernel.org
Subject: Re: [PATCH] Add archive-tree, a cpio archive creator
Date: Tue, 26 Apr 2005 16:42:04 +0200 [thread overview]
Message-ID: <426E533C.70502@lsrfire.ath.cx> (raw)
In-Reply-To: <20050425153011.34c93b38.paul@permanentmail.com>
Paul Dickson schrieb:
> Use the "newc" format. The "odc" will generate a lot of errors on a
> large filesystem (which I discovered this past weekend).
How is that? I can only imagine problems with the size of individual
files inside an archive because the size field in the header is limited
to 33 bits.
In any case, I switched to the tar format. It's more complicated but it
turned out that creating these things is still easy. Parsing them might
be more of a challenge, but we already have tar for that. :-)
See my other mail for more on the tar creator. I also rebased it to
core GIT because it's no helper script.
Rene
prev parent reply other threads:[~2005-04-26 14:37 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
2005-04-26 14:42 ` 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=426E533C.70502@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
--cc=paul@permanentmail.com \
/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).