git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Eric Wong <normalperson@yhbt.net>
Cc: Nicolas Pitre <nico@cam.org>,
	Peter Stahlir <peter.stahlir@googlemail.com>,
	git@vger.kernel.org
Subject: Re: Git as a filesystem
Date: Sat, 22 Sep 2007 00:42:09 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709220040450.28395@racer.site> (raw)
In-Reply-To: <20070921233343.GA8327@muzzle>

Hi,

On Fri, 21 Sep 2007, Eric Wong wrote:

> Nicolas Pitre <nico@cam.org> wrote:
> > On Fri, 21 Sep 2007, Peter Stahlir wrote:
> > 
> > > This is was I was looking for. My motivation is whether it is possible
> > > to run a system, for example Debian on a computer on top of gitfs,
> > > and then have a huge mirror on it, for example a complete 252GB
> > > Debian mirror as space efficient as possible.
> > > 
> > > I wonder how big a deltified Debian mirror in one pack file would be. :)
> > 
> > It would be just as big as the non gitified storage on disk.
> > 
> > The space saving with git comes from efficient delta storage of 
> > _versioned_ files, i.e. multiple nearly identical versions of the same 
> > file where the stored delta is only the small difference between the 
> > first full version and subsequent versions.  Unless you plan on storing 
> > many different Debian versions together, you won't benefit from any 
> > delta at all. And since Debian packages are already compressed, git 
> > won't be able to compress them further.
> > 
> > So don't waste your time.
> 
> On a similar note, has anybody experimented with using git to
> store maildirs or news spools?  I'd imagine the quoted portions of
> most message threads could be delta-compressed quite efficiently.

I store all my mail in a git repository.  Works beautifully.  Except that 
the buffers on my laptop are constantly full :-(  So a simple commit takes 
some waiting.

Should be no issue on normal (desktop) machines.

Ciao,
Dscho

  reply	other threads:[~2007-09-21 23:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 10:51 Git as a filesystem Peter Stahlir
2007-09-21 11:11 ` Johannes Schindelin
2007-09-21 11:41   ` Peter Stahlir
2007-09-21 12:53     ` Karl Hasselström
2007-09-21 13:28       ` Peter Stahlir
2007-09-21 13:41         ` Michael Poole
2007-09-21 14:38         ` jlh
2007-09-21 17:29         ` Dmitry Potapov
2007-09-21 23:56           ` Martin Langhoff
2007-09-22  3:09             ` Sam Vilain
2007-09-21 13:22     ` Nicolas Pitre
2007-09-21 13:35       ` Peter Stahlir
2007-09-21 13:45         ` Nicolas Pitre
2007-09-21 15:46         ` Christian von Kietzell
2007-09-21 23:33       ` Eric Wong
2007-09-21 23:42         ` Johannes Schindelin [this message]
2007-09-22  2:06           ` Eric Wong
2007-09-22 12:06             ` Johannes Schindelin
2007-09-21 14:22   ` Miklos Vajna

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0709220040450.28395@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=normalperson@yhbt.net \
    --cc=peter.stahlir@googlemail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).