Re: git guidance

From: Valdis.Kletnieks@vt.edu
To: Al Boldi <a1426z@gawab.com>
Cc: Jakub Narebski <jnareb@gmail.com>, Andreas Ericsson <ae@op5.se>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Phillip Susi <psusi@cfl.rr.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jing Xue <jingxue@digizenstudio.com>,
	linux-kernel@vger.kernel.org, git@vger.kernel.org
Subject: Re: git guidance
Date: Sat, 08 Dec 2007 00:16:27 -0500	[thread overview]
Message-ID: <7135.1197090987@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 08 Dec 2007 07:56:21 +0300." <200712080756.21980.a1426z@gawab.com>

[-- Attachment #1: Type: text/plain, Size: 621 bytes --]

On Sat, 08 Dec 2007 07:56:21 +0300, Al Boldi said:

> It probably goes without saying, that gitfs should have some basic 
> configuration file to setup its transparent behaviour

But then it's not *truly* transparent, is it?

And that leaves another question - if you make a config file that excludes
all the .o files - then what's backing the .o files?  Those data blocks need
to be *someplace*.  Maybe you can do something ugly like use unionfs to
combine your gitfs with something else to store the other files...

But at that point, you're probably better off just creating a properly
designed versioning filesystem.

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]