Re: I don't want the .git directory next to my code.

On Wed, 16 Jan 2008, Linus Torvalds wrote:

Example management scripts: let's say that you have a logo that shows up in multiple different sizes. You can just have it as <n> number of different files that you check in and update separately, or you can have it as *one* scalable master file, and then the deployment script will create all the generated files and put them in the deployment area.

So the common issue with SCM's is that you want to share two totally different things:

 - the actual "source" (which obviously doesn't have to be source code per 
   se), which is the thing you want to have for yourself and people you 
   work with, and which you want the history of.

 - the "output" for external entities, which may often contain a lot of 
   the "source" verbatim, but quite often doesn't contain it all (some of 
   the stuff you need to manage things may be rather private and purely 
   for *your* management info), and almost invariably contains some 
   post-processing.

Some people don't split this up, and they tend to make horrible horrible mistakes, like checking in the *results* of the post-processing too (ie binary result blobs that can be regenerated from the other files), because they don't make a clear separation between the parts they do development on, and the end result.

			Linus