From: Michael Witten <mfwitten@gmail.com>
To: "Hervé Cauwelier" <herve@itaapy.com>
Cc: git@vger.kernel.org
Subject: Re: Multiblobs
Date: Fri, 30 Apr 2010 13:16:55 -0500 [thread overview]
Message-ID: <u2lb4087cc51004301116t17ba0efamf4c9b38842bad409@mail.gmail.com> (raw)
In-Reply-To: <4BDA9F5C.2080808@itaapy.com>
2010/4/30 Hervé Cauwelier <herve@itaapy.com>:
>
> Unless you are talking about a dedicated application to store and generate
> on-the-fly office documents, built on top of Git, you're better not touching
> the contents the user is entrusting git to store, and write a .gitattribute
> not to compress them in a pack.
Doesn't OOo provide at least some library of official code for
handling such files, so that other programs might be able to
interoperate?
If so, then it would be almost trivial for an OpenDocument 'plugin' to
be 'built on top of Git'.
If not, then OOo is crap.
next prev parent reply other threads:[~2010-04-30 18:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 15:12 Multiblobs Sergio Callegari
2010-04-28 18:07 ` Multiblobs Avery Pennarun
2010-04-28 19:13 ` Multiblobs Sergio Callegari
2010-04-28 21:27 ` Multiblobs Avery Pennarun
2010-04-28 23:10 ` Multiblobs Michael Witten
2010-04-28 23:26 ` Multiblobs Sergio
2010-04-29 0:44 ` Multiblobs Avery Pennarun
2010-04-29 11:34 ` Multiblobs Peter Krefting
2010-04-29 15:28 ` Multiblobs Avery Pennarun
2010-04-30 8:20 ` Multiblobs Peter Krefting
2010-04-30 17:26 ` Multiblobs Avery Pennarun
2010-04-30 9:14 ` Multiblobs Hervé Cauwelier
2010-04-30 17:32 ` Multiblobs Avery Pennarun
2010-04-30 18:16 ` Michael Witten [this message]
2010-04-30 19:06 ` Multiblobs Hervé Cauwelier
2010-04-28 18:34 ` Multiblobs Geert Bosch
2010-04-29 6:55 ` Multiblobs Mike Hommey
2010-05-06 6:26 ` Multiblobs Jeff King
2010-05-06 22:56 ` Multiblobs Sergio Callegari
2010-05-10 6:36 ` Multiblobs Jeff King
2010-05-10 13:58 ` Multiblobs Sergio Callegari
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=u2lb4087cc51004301116t17ba0efamf4c9b38842bad409@mail.gmail.com \
--to=mfwitten@gmail.com \
--cc=git@vger.kernel.org \
--cc=herve@itaapy.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).