From: Josef Weidendorfer Date: Mon, 11 Dec 2006 12:13:34 GMT Subject: Re: Using GIT to store /etc (Or: How to make GIT store all file permission bits) Message-ID: <200612111313.34292.Josef.Weidendorfer@gmx.de> In-Reply-To: <457D3573.2010001@op5.se> On Monday 11 December 2006 11:39, Andreas Ericsson wrote: > > Import/export scripts literally require wrapping every single GIT > > command with a script that changes directory a few times, reads from a > > different checked-out tree, and permutes some extended-attribute data > > slightly before storing it in the underlying GIT tree. Even without > > adding any new functionality whatsoever that doubles the amount of code > > just for finding your repository and checking command-line arguments, > > and that's a crazy trade-off to make in any situation. > > > > GIT_DIR=/some/where/else/.git git log -p Doing this everytime you want to run a git command *is* a lot of time wasted for typing. The .gitlink proposal would come in handy here: you have a simple file instead of .git/, which links to the real repository.