From: Maaartin <grajcar1@seznam.cz>
Date: Fri, 08 Oct 2010 21:39:01 GMT
Subject: Re: Alternate .gitignore
Message-ID: <loom.20101008T225637-152@post.gmane.org>
In-Reply-To: <AANLkTimG188_8qg-DTtJtvX-wkpotgp7+f8Bu4b4ayMn@mail.gmail.com>

Ævar Arnfjörð Bjarmason <avarab <at> gmail.com> writes:

> Have you looked into storing your binaries in a git-submodule(1) ?

I've look at it just now and it doesn't seem to be the thing I need. According 
to my very basis understanding submodules seem to be useful for embedding other 
projects, but I'm working with a single project only. I'm speaking about a 
single project and need to store it in different repositories at different 
"ignorance levels".

To make it clear, just imagine that compilation would be many thousand times 
slower. In such a case you could prefer to store the history of the *.o files as 
well, but you'd still want to avoid the pollution of the source tree. So you'd 
maybe use .git for the sources as usually and .git2 (or whatever) for the object 
files (maybe together with the sources). This comes very close to my situation.

I could switch to using .git2 using $GIT_DIR, but with "*.o" in my .gitignore I 
see no way how to include the ignored files. Maybe I could use $GIT_DIR/info/
exclude somehow instead of .gitignore, but this could be quite cumbersome.