From: Stephen Bash <bash@genarts.com>
To: "Jeff King" <peff@peff.net>, "Junio C Hamano" <gitster@pobox.com>,
"René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Cc: git discussion list <git@vger.kernel.org>
Subject: Re: Passing commit IDs to git-archive
Date: Mon, 12 Mar 2012 09:24:40 -0400 (EDT) [thread overview]
Message-ID: <57b23100-a04d-4eca-bb0e-35455464ec5c@mail> (raw)
In-Reply-To: <20120312114742.GC12921@sigill.intra.peff.net>
----- Original Message -----
> From: "Jeff King" <peff@peff.net>
> Sent: Monday, March 12, 2012 7:47:42 AM
> Subject: Re: Passing commit IDs to git-archive
>
> On Fri, Mar 09, 2012 at 05:14:05PM -0500, Stephen Bash wrote:
>
> > on Mac OS 10.6.8 (obviously this is local testing, the goal is to
> > use ssh remotely). After parsing the error "no such ref" I
> > attempted the same operation using master as the tree-ish and
> > archive worked as expected (either specifying the path separately or
> > using the colon syntax to reference the tree directly). Is there a
> > reason git-archive requires a named ref rather than just a commit
> > (or tree) ID?
>
> Yes; generally git repositories do not allow clients to access
> arbitrary sha1s. Instead, they require that the requested objects be
> accessible by a ref.
Jeff: thanks for the concise summary. I thought that might be the case, but wanted to confirm.
Junio and René: thanks for the input and ideas. Seems I'll be investigating my options today.
Thanks,
Stephen
prev parent reply other threads:[~2012-03-12 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8c6d921d-9e8e-4caf-bc04-b1d2cfdd294f@mail>
2012-03-09 22:14 ` Passing commit IDs to git-archive Stephen Bash
2012-03-09 22:34 ` Junio C Hamano
2012-03-10 6:40 ` René Scharfe
2012-03-12 11:47 ` Jeff King
2012-03-12 13:24 ` Stephen Bash [this message]
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=57b23100-a04d-4eca-bb0e-35455464ec5c@mail \
--to=bash@genarts.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=rene.scharfe@lsrfire.ath.cx \
/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).