From: Stephen Bash <bash@genarts.com>
Date: Mon, 12 Mar 2012 13:24:40 GMT
Subject: Re: Passing commit IDs to git-archive
Message-ID: <57b23100-a04d-4eca-bb0e-35455464ec5c@mail>
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