From: Andrew Lutomirski <luto@mit.edu>
Date: Wed, 14 Sep 2011 20:49:31 GMT
Subject: Re: [Survey] Signed push
Message-ID: <CAObL_7Er5mMuNaNgLDptBHw-zrqEeHHqXkC+TNf9G81_+NmFKw@mail.gmail.com>
In-Reply-To: <7vwrdasvr7.fsf@alter.siamese.dyndns.org>

On Wed, Sep 14, 2011 at 1:40 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Andy Lutomirski <luto@MIT.EDU> writes:
>
>>> An alternative that I am considering is to let the requester say this
>>> instead:
>>>
>>>     are available in the git repository at:
>>>       git://git.kernel.org/pub/flobar.git/ 5738c9c21e53356ab5020912116e7f82fd2d428f
>>>
>>> without adding the extra line.
>>>
>>> That is, to allow fetching the history up to an explicitly named commit
>>> object. This would only involve a change to fetch-pack at the receiving
>>> end; just match the commit object name given from the command line against
>>> the ls-remote response and ask upload-pack to give the history leading to
>>> it....
>>
>> I would love this feature on the pull/fetch interface, but for a
>> completely different reason.  Sometimes I want to pull a particular
>> object (usually a commit, but sometimes just a tree or blob) from
>> *myself*, and having to stick it on a branch is annoying.
>
> I am afraind that it is not going to happen; see
>
>    http://article.gmane.org/gmane.comp.version-control.git/181317
>
> for a rationale.
>

Do you mean that it's a security feature?  What if a .git/config
option existed to allow this use?  Or even a git upload-pack option
that turned it *on* and was stripped by git-shell?

--Andy