From: Clark Williams <clark.williams@gmail.com>
To: sverre@rabbelier.nl
Cc: "Asheesh Laroia" <asheesh@asheesh.org>,
"Karl Hasselström" <kha@treskal.com>,
"Catalin Marinas" <catalin.marinas@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH - stgit] Patch to allow import of compressed files
Date: Tue, 10 Jun 2008 09:01:43 -0500 [thread overview]
Message-ID: <484E8947.5070508@gmail.com> (raw)
In-Reply-To: <bd6139dc0806100107y415a292eqe22af7a7b2215e65@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sverre Rabbelier wrote:
> On Tue, Jun 10, 2008 at 8:38 AM, Asheesh Laroia <asheesh@asheesh.org> wrote:
>> Peanut gallery question: Why not just always try these methods and catch
>> some format exception if they fail, proceeding to the next possible
>> decompressor (proceeding on to no decompressor)?
>>
>> That way if a file is called .GZ, it will still be handled properly; in
>> fact, all files would still be handled properly. And these formats leave
>> notes in the first few bytes of the file as to if they should be tried, so
>> it's not as if it would come at some performance cost.
>
> How about adding in '.tar' decompression as well, -after- the '.gz'
> decompression? That way you can have .tar.gz's and still be fine.
>
I thought about this, as well as the .zip format. The problem is in multiple files
and how to handle them. Do you look for a series and automagically add '--series'
semantics? What about ignore/replace? If no series file, do you just try to apply
all of them? In what order? Look for '.patch' suffix and only use those? And what
about the old '.tgz' suffix? Lots of different ways to go here.
I don't think it would be a bad thing to add .tar and .zip handling, but I'd rather
bat it around a little on this list before doing it. That way we can find out how
people would like to use it.
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkhOiUcACgkQqA4JVb61b9cWawCeK+n8uo8XGGlURYG2ImuhUUNY
eZEAn31ZfjC7MgiP1VZ02uksrRJQiQVe
=Tu6s
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-06-10 14:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 18:38 [PATCH - stgit] Patch to allow import of compressed files Clark Williams
2008-06-10 6:33 ` Karl Hasselström
2008-06-10 6:38 ` Asheesh Laroia
2008-06-10 8:07 ` Sverre Rabbelier
2008-06-10 9:53 ` Karl Hasselström
2008-06-10 9:57 ` Sverre Rabbelier
2008-06-10 10:28 ` Karl Hasselström
2008-06-10 10:33 ` Sverre Rabbelier
2008-06-10 14:06 ` Clark Williams
2008-06-10 14:01 ` Clark Williams [this message]
2008-06-10 13:57 ` Clark Williams
2008-06-10 14:04 ` Asheesh Laroia
2008-06-10 13:54 ` Clark Williams
2008-06-10 13:54 ` Clark Williams
2008-06-11 6:27 ` Karl Hasselström
2008-06-11 17:28 ` Clark Williams
2008-06-11 19:14 ` Karl Hasselström
2008-06-19 14:17 ` David Kågedal
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=484E8947.5070508@gmail.com \
--to=clark.williams@gmail.com \
--cc=asheesh@asheesh.org \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
--cc=sverre@rabbelier.nl \
/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).