From: Johannes Sixt <j.sixt@viscovery.net>
To: Sergio Callegari <sergio.callegari@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Management of opendocument (openoffice.org) files in git
Date: Tue, 16 Sep 2008 09:09:04 +0200 [thread overview]
Message-ID: <48CF5B90.5050800@viscovery.net> (raw)
In-Reply-To: <loom.20080915T222909-709@post.gmane.org>
Sergio Callegari schrieb:
> if [ $# = 0 ] ; then
> tmpcopy=$(mktemp rezip.zip.XXXXXX)
> cat > $tmpcopy
> filename="$tmpcopy"
> else
> tmpcopy=""
> filename="$1"
> fi
>
> workdir=$(mktemp -d -t rezip.workdir.XXXXXX)
> curdir=$(pwd)
>
> cd $workdir
> unzip $UNZIP_OPTS "$curdir/$filename"
> zip $ZIP_OPTS "$curdir/$filename" .
> cd $curdir
> rm -fr $workdir
> if [ ! -z "$tmpcopy" ] ; then
> cat $filename
> rm $tmpcopy
> fi
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
> 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?
-- Hannes
next prev parent reply other threads:[~2008-09-16 7:10 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 [this message]
2008-09-16 7:41 ` Sergio Callegari
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=48CF5B90.5050800@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.