Re: git guidance

From: Al Boldi <a1426z@gawab.com>
Date: Dec 8, 2007, 10:41 UTC
Message-ID: <200712081341.54589.a1426z@gawab.com>
In-Reply-To: <7135.1197090987@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:

Show 5 quoted lines

> 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?

Don't mistake transparency with some form of auto-heuristic. Transparency only means that it inserts functionality without impeding your normal workflow.

> 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...

Or any number of other possible implementation scenarios...

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

But gitfs is not about designing a versioning filesystem, it's about designing a transparent interface into git to handle an SCM use-case.

Thanks!

-- Al