git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Kagy <bobkagy@gmail.com>
To: git@vger.kernel.org
Subject: git archive, cygwin, and --git-dir vs --remote
Date: Mon, 18 May 2009 09:37:14 -0500	[thread overview]
Message-ID: <e664dae0905180737mae29811ie4cae889b3e3904f@mail.gmail.com> (raw)

I'm using git on cygwin, and am confused by behavior from git archive.

git --version
git version 1.6.1.2

This command works as expected:
git --git-dir=/cygdrive/w archive --format=tar --verbose --prefix=tmp/
HEAD | tar -xpf -
The latest copy is retrieved and dumped to the tmp subdirectory.

However, I first went down the path of using the --remote option, as
described in the git-archive man page:
git archive --format=tar --verbose --prefix=tmp/ --remote=/cygdrive/w
HEAD | tar -xpf -

When I use the --remote branch it seems to create the same files.  But
then rather than exiting it hangs out until I kill the process, using
about the same CPU % as it did when creating files.

I'm trying to use this for a scripted build process where all I need
is the latest copy, not an archive.  And we're just starting with git,
so while it works fine now I think we're supposed to be switch from
shared drives to something more controlled, at which point I don't
know that the --git-dir option will work.

I've tried searching the mailing list archive, and got overwhelmed by
patches, so I apologize if this has already been discussed and I just
couldn't find it.

             reply	other threads:[~2009-05-18 14:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 14:37 Bob Kagy [this message]
2009-05-21  9:08 ` git archive, cygwin, and --git-dir vs --remote René Scharfe
2009-05-21 13:32   ` Tony Finch
2009-05-21 14:29     ` René Scharfe
2009-06-17 10:11       ` [PATCH] upload-archive: fix infinite loop on Cygwin René Scharfe
2009-06-18 17:18         ` Tony Finch

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=e664dae0905180737mae29811ie4cae889b3e3904f@mail.gmail.com \
    --to=bobkagy@gmail.com \
    --cc=git@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).