From: "Avery Pennarun" <apenwarr@gmail.com>
To: "Sergio Callegari" <sergio.callegari@gmail.com>
Cc: "Johannes Sixt" <j.sixt@viscovery.net>, git@vger.kernel.org
Subject: Re: Management of opendocument (openoffice.org) files in git
Date: Tue, 16 Sep 2008 12:04:44 -0400 [thread overview]
Message-ID: <32541b130809160904v7acc73cfm4856c33d40555e94@mail.gmail.com> (raw)
In-Reply-To: <48CF630F.4090808@gmail.com>
On Tue, Sep 16, 2008 at 3:41 AM, Sergio Callegari
<sergio.callegari@gmail.com> wrote:
> Johannes Sixt wrote:
>>
>> You don't need a temporay zip filename in filter mode:
>>
>> unzip $UNZIP_OPTS /dev/stdin # works for me, but not 100% portable
>> zip $ZIP_OPTS - . # writes to stdout
>>
>>
>
> The unzip documentation says "Archives read from standard input are not yet
> supported", so I was a bit worried about using the /dev/stdin thing. Might
> it be that there are subtle cases where unzip needs to seek or rewind?
IIRC zip files keep their index at the end of the file, which means
zipping in a pipeline is efficient (you can write all the blocks
first, then drop the final index at the end) but unzipping that way is
really hard.
unzipping from /dev/stdin seems to work if stdin is seekable, otherwise not.
unzip /dev/stdin <filename.zip # works
cat filename.zip | unzip /dev/stdin # doesn't work
Have fun,
Avery
next prev parent reply other threads:[~2008-09-16 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 22:40 Management of opendocument (openoffice.org) files in git Sergio Callegari
2008-09-16 6:45 ` Matthieu Moy
2008-09-16 7:41 ` Sergio Callegari
2008-09-16 7:09 ` Johannes Sixt
2008-09-16 7:41 ` Sergio Callegari
2008-09-16 7:52 ` Johannes Sixt
2008-09-16 16:04 ` Avery Pennarun [this message]
2008-09-16 19:28 ` Stephen R. van den Berg
2008-09-16 21:13 ` Robin Rosenberg
2008-09-23 11:08 ` Peter Krefting
-- strict thread matches above, loose matches on Subject: below --
2008-09-16 6:24 Paolo Bonzini
2008-09-16 7:05 ` Sergio Callegari
2008-09-16 8:12 ` Paolo Bonzini
2008-10-02 12:52 ` Michael J Gruber
2008-10-10 8:12 ` Peter Krefting
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=32541b130809160904v7acc73cfm4856c33d40555e94@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=sergio.callegari@gmail.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).