From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Thu, 17 Jan 2008 02:59:05 GMT
Subject: Re: I don't want the .git directory next to my code.
Message-ID: <46a038f90801161859n2f7d8c33kb5d359fb25d07488@mail.gmail.com>
In-Reply-To: <86sl0xfd4e.fsf@blue.stonehenge.com>

On Jan 17, 2008 2:35 PM, Randal L. Schwartz <merlyn@stonehenge.com> wrote:
> >>>>> "Brian" == Brian Downing <bdowning@lavos.net> writes:
>
> Brian> Yes, you could use rsync or some other tool, but Git already has the
> Brian> tools available, so why not take advantage of them?
>
> It's very likely that rsync will be faster/better/cheaper/more-flexible
> than git.  "Yes, you could use git, but rsync already does the job
> better, so why not take advantage of it?"  Back at ya.

We do web development, and use various deployment tools, usually git,
git+rsync or git + debian packages.

I find the discussion of git-archive as a deployment tool a bit
worrying - remember that untarring a newer version of the tarball on
top of the old version does not remove old files. In web applications
(and I think the OP is talking about web development) often security
bugs come from sloppy inclusion of files (such as sample AdoDB code).
If you deploy your "security fix" by unpacking a tarball, chances are
you'll wake up to a p0wned server.

cheers,


martin