Re: git archive invocation using sha1 to specify commit

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 29, 2012, 08:46 UTC
Message-ID: <7v7gz6uiv0.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CA+OUE96-mLc0RJZz0g0oBWxdZKeCMQ9xJbg6DjCacN119TFY+A@mail.gmail.com>

Zdenek Crha <zdenek.crha@gmail.com> writes:

Show 5 quoted lines

> In out company we are using git together with source indexing. We
> store a git command for retrieval of source code file that was used
> for building into pdb file(s). Currently,...
> ... I'm not sure whenever ability to export arbitrary sha1 will be
> allowed too.

No, that will be a premium feature that your company _could_ pay for with the source of that "source indexing" system ;-)

Jokes aside, this was part of a security tightening to make sure nobody could reach something that cannot be obtained by cloning, without incurring large computation overhead.

Theoretically we could selectively loosen the restriction [*1*], but it is not very high on our priority list.

[Footnote]

*1* When the given starting point is a raw SHA-1, we could run a single merge_bases_many() to see if any of the refs can reach it, and only serve the tree the check passes, or something.