All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike <fromlists@talkingspider.com>
To: Luke Lu <git@vicaya.com>
Cc: David Symonds <dsymonds@gmail.com>,
	git@vger.kernel.org, Johannes.Schindelin@gmx.de
Subject: Re: I don't want the .git directory next to my code.
Date: Wed, 16 Jan 2008 12:23:09 -0500	[thread overview]
Message-ID: <478E3D7D.4000700@talkingspider.com> (raw)
In-Reply-To: <D017F6F6-D674-428B-936B-181BF20CF4B5@vicaya.com>



Luke Lu wrote:
> 
> On Jan 15, 2008, at 8:18 PM, Mike wrote:
> 
>>
>> David Symonds wrote:
>>> On Jan 16, 2008 2:27 PM, Mike <fromlists@talkingspider.com> 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.
> 
> git-archive generates an archive file *without* the .git directory. From 
> git-archive(1):
> 
>   git archive --format=tar --prefix=junk/ HEAD | (cd /var/tmp/ && tar xf -)
>               Create a tar archive that contains the contents of the latest
>               commit on the current branch, and extracts it in 
> /var/tmp/junk
>               directory.
> 
>   git archive --format=tar --prefix=git-1.4.0/ v1.4.0 | gzip > 
> git-1.4.0.tar.gz
>               Create a compressed tarball for v1.4.0 release.
> 
>   git archive --format=tar --prefix=git-1.4.0/ v1.4.0^{tree} | gzip 
>  >git-1.4.0.tar.gz
>               Create a compressed tarball for v1.4.0 release, but without a
>               global extended pax header.
> 
>   git archive --format=zip --prefix=git-docs/ HEAD:Documentation/ > 
> git-1.4.0-docs.zip
>               Put everything in the current head's Documentation/ directory
>               into git-1.4.0-docs.zip, with the prefix git-docs/.
> 
> IMHO, git export is probably a better name for the command. git-archive 
> sounds like backup everything associated with git.
> 
> __Luke
> -

OK I don't think you read my response closely.  I wasn't going to 
respond except I see Johannes missed the point too.

I completely understand that git archive will not inlcude the .git dir. 
What you missed in my response is the case where someone tars up a 
directory above the .git directory. Not all of the content under doc 
root is in a git archive.

  reply	other threads:[~2008-01-16 17:23 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16  3:27 I don't want the .git directory next to my code Mike
2008-01-16  3:50 ` Randal L. Schwartz
2008-01-16  4:07   ` Mike
2008-01-16  4:24     ` David Symonds
2008-01-16  4:29       ` Mike
2008-01-16  4:36     ` Sean
2008-01-16 17:31       ` Mike
2008-01-16  5:27     ` Neil Macneale
2008-01-16 17:23       ` Mike
2008-01-16 17:51         ` Johannes Schindelin
2008-01-16 18:15         ` Linus Torvalds
2008-01-16 18:25           ` Linus Torvalds
2008-01-17  5:42             ` Mike
2008-01-17  6:38               ` Kris Shannon
2008-01-17 10:34               ` Wincent Colaiuta
2008-01-17 15:17               ` Jeff King
2008-01-17 17:36                 ` Linus Torvalds
2008-01-17 17:49                   ` Johannes Schindelin
2008-01-17 18:02                     ` Linus Torvalds
2008-01-17 18:10                       ` Johannes Schindelin
2008-01-17 19:12                 ` Mike
2008-01-17 19:20                   ` Johannes Schindelin
2008-01-17 20:00                     ` Mike
2008-01-17 20:08                       ` Johannes Schindelin
2008-01-17 20:49                         ` Mike
2008-01-17 20:57                           ` Johannes Schindelin
2008-01-17 21:00                             ` Mike
2008-01-17 21:05                               ` Johannes Schindelin
2008-01-18  7:52                   ` David Symonds
2008-01-22 10:27                   ` Russ Dill
2008-01-17 21:05               ` Martin Langhoff
2008-01-18  8:41               ` Andreas Ericsson
2008-01-16 19:23           ` Junio C Hamano
2008-01-17  2:00           ` Ping Yin
2008-01-17  2:38             ` Linus Torvalds
2008-01-16  3:56 ` Dan McGee
2008-01-16  6:00   ` Mike
2008-01-16  6:07     ` Mike Krier
2008-01-16  6:09     ` Mike
2008-01-16  4:03 ` Nguyen Thai Ngoc Duy
2008-01-16  4:06 ` David Symonds
2008-01-16  4:18   ` Mike
2008-01-16  4:44     ` Daniel Barkalow
2008-01-16  4:55     ` Luke Lu
2008-01-16 17:23       ` Mike [this message]
2008-01-17  1:42     ` Sam Vilain
2008-01-16  4:13 ` Daniel Barkalow
2008-01-16  4:24   ` Mike
2008-01-16 10:37     ` Johannes Schindelin
2008-01-16 13:21   ` Bert Wesarg
2008-01-16 22:33   ` Wayne Davison
2008-01-16  9:59 ` Matthieu Moy
2008-01-16 10:36   ` Johannes Schindelin
2008-01-16 11:41     ` Bill Lear
2008-01-16 12:25       ` Matthieu Moy
2008-01-16 12:45         ` Johannes Schindelin
2008-01-16 17:40           ` Junio C Hamano
2008-01-16 17:52             ` Johannes Schindelin
2008-01-16 11:59     ` Matthieu Moy
2008-01-16 12:12       ` Johannes Schindelin
2008-01-16 13:13 ` Jakub Narebski
2008-01-17  0:59   ` Brian Downing
2008-01-17  1:35     ` Randal L. Schwartz
2008-01-17  2:59       ` Martin Langhoff
2008-01-17  5:44         ` Randal L. Schwartz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=478E3D7D.4000700@talkingspider.com \
    --to=fromlists@talkingspider.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=git@vicaya.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.