From: Jakub Narebski <jnareb@gmail.com>
To: Enrico Weigelt <weigelt@metux.de>
Cc: git@vger.kernel.org
Subject: Re: git repo in a single file
Date: Sat, 17 Mar 2012 09:48:19 -0700 (PDT) [thread overview]
Message-ID: <m3bonvkwda.fsf@localhost.localdomain> (raw)
In-Reply-To: <20120317155445.GA18712@mailgate.onlinehome-server.info>
Enrico Weigelt <weigelt@metux.de> writes:
> in several discussion with people eg. on office software fronts,
> I've seen the value of having an git repo in one file. For example,
> an office document, internally consisting of several files (like
> ODF) could be put into an git repo instead of zip. That would
> give a good basis for things like versioning, etc.
There is something like that in the form of git-bundle.
Perhaps it could be (ab)used to what you want.
--
Jakub Narebski
prev parent reply other threads:[~2012-03-17 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 15:54 git repo in a single file Enrico Weigelt
2012-03-17 16:13 ` Vincent van Ravesteijn
2012-03-17 16:48 ` Jakub Narebski [this message]
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=m3bonvkwda.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=weigelt@metux.de \
/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).