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

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Jan 17, 2008, 02:38 UTC
Message-ID: <alpine.LFD.1.00.0801161834380.2806@woody.linux-foundation.org>
In-Reply-To: <46dff0320801161800y9f5bf0cvb1804a57c41c3f4c@mail.gmail.com>

On Thu, 17 Jan 2008, Ping Yin wrote:

>
> Using git to manage deployment environment and even as deployment
> tools is not always a bad idea.

I don't think it's alway sa bad idea, no. But it's a good idea only if you then accept things like ".git" subdirectories lying around in your deployment area (or you accept the use of tricks like GIT_DIR).

Show 10 quoted lines

> 1. In case where development and deployment environment are almost the
> same, such as html files, js files, binding the two environments as
> one is convenient.
> 
> 2. Event In the case where the two environement are different very
> much, managing deployment environment in git sometimes still seems
> good, since we can easily back to any earlier version or fix some
> urgent bug ASAP (surely for the non-generated files).
> 
> 3. Use 'git pull' as deploy command seems simple enough.

Hey, I do it for all my kernels ("git pull" + "make" is just simpler than pushing tar-balls around), so I'm not entirely disagreeing. I *like* having the entire development environment around everywhere.

But it does seem like a lot of Mike's problems basically boil down to the fact that he doesn't really want to use it as a deployment tool.

		Linus