[EMAIL PROTECTED] wrote: > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
