From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: "Asheesh Laroia" <asheesh@asheesh.org>,
"Clark Williams" <clark.williams@gmail.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 11:57:05 +0200 [thread overview]
Message-ID: <bd6139dc0806100257k4700d364occ08457279e8a735@mail.gmail.com> (raw)
In-Reply-To: <20080610095349.GA30119@diana.vm.bytemark.co.uk>
On Tue, Jun 10, 2008 at 11:53 AM, Karl Hasselström <kha@treskal.com> wrote:
> On 2008-06-10 10:07:25 +0200, Sverre Rabbelier wrote:
>
>> How about adding in '.tar' decompression as well, -after- the '.gz'
>> decompression? That way you can have .tar.gz's and still be fine.
>
> A tar file would presumably contain more than one patch -- it'd be
> more like a directory of patches than a single patch file.
Why?
$ tar czvf mypatch.patch.tar.gz mypatch.patch
> I'm not saying it wouldn't be nice to support it, but it's not what
> the original poster needed, and building it would be a bunch of extra
> work.
A bunch of extra work? http://docs.python.org/lib/module-tarfile.html
I say it'd be about as much work as the original patch ;).
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2008-06-10 9:58 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 [this message]
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
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=bd6139dc0806100257k4700d364occ08457279e8a735@mail.gmail.com \
--to=alturin@gmail.com \
--cc=asheesh@asheesh.org \
--cc=catalin.marinas@gmail.com \
--cc=clark.williams@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).