On Tue, 15 Jan 2008, Mike wrote: > David Symonds wrote: > > On Jan 16, 2008 2:27 PM, Mike <fromlists@xxxxxxxxxxxxxxxxx> wrote: > > > 2. If I tar/gz my code and deliver it to a client, I don't want the .git > > > dir slipping into the tarball, allowing my client to be able to peruse > > > the history of what we did and when. > > > > Use git-archive. > > > > Thanks but this isn't sufficient. If we have one directory of our web root in > a git repository, say docroot/php, and we tar up docroot, it will include > php/.git. We don't want that. We would have to go out of our way to avoid > the .git directory. The point is, we don't want anything in docroot that > shouldn't be made live. I don't know about you, but my source directories get lots of other junk: editor backup files, half-written scripts, debugging output, etc. Furthermore, there's the issue of whether you can accidentally distribute something you haven't added to your version control yet and therefore can't reproduce. It's just a lot cleaner to deploy and distribute out of the version control system instead of out of a working directory. I don't know why you don't seem to have git-archive (or its manpage); it's in the version you have. Maybe it didn't get into the deb-generation files at the time? You might have git-tar-tree instead, though. -Daniel *This .sig left intentionally blank* - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
