From: Sergio Callegari <sergio.callegari@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: git@vger.kernel.org
Subject: Re: Management of opendocument (openoffice.org) files in git
Date: Tue, 16 Sep 2008 09:41:03 +0200 [thread overview]
Message-ID: <48CF630F.4090808@gmail.com> (raw)
In-Reply-To: <48CF5B90.5050800@viscovery.net>
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?
>> then put in your .git/config something like
>>
>> [filter "opendocument"]
>> clean = "rezip -p ODF_UNCOMPRESS"
>> smudge = "rezip -p ODF_COMPRESS"
>>
>
> Is the smudge filter really necessary? Can't OOo work with files at
> compression level 0?
>
Yes, you can live perfectly without smudge. But at times it is not that
nice. Just think of finding a directory with say 15 lectures as impress
slides taking 10 times the space it needs, particularly if you need to
pass those files to someone else. As a matter of fact, ODF xml is very
verbose and compresses particularly well having long tags.
But you might want to compress -1 rather than the default in smudge to
speed it up a little. Can be done either adding a new profile to the
script (say ODF_COMPRESS_FAST) or by adding --zip_opts -1 to the smudge
command line.
Also, we might want to add some -n suffixes to zip, to prevent it from
trying to compress a few things like .png or .jpeg images and that have
their own compression. That should gain us some speed in smudging.
In any case - but this is just my feeling - it is much more disturbing
the delay that the clean filter introduces in operations like add or
status or commit, than the one introduced by the (slower) smudge filter
in checkout. There must be some psychological reason for that.
Possibly we are "programmed" to accept waiting when we need to get
something and conversely we are impatient when someone should accept
something from us.
Sergio
next prev parent reply other threads:[~2008-09-16 7:42 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 [this message]
2008-09-16 7:52 ` Johannes Sixt
2008-09-16 16:04 ` Avery Pennarun
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=48CF630F.4090808@gmail.com \
--to=sergio.callegari@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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).