Re: What's cooking in git.git (Oct 2011, #06; Tue, 18)

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 18, 2011, 18:09 UTC
Message-ID: <7v7h42gois.fsf@alter.siamese.dyndns.org>
In-Reply-To: <7vmxcygs1m.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

Show 22 quoted lines

> Phil Hord <phil.hord@gmail.com> writes:
>
>> On Tue, Oct 18, 2011 at 3:50 AM, Junio C Hamano <gitster@pobox.com> wrote:
>>> What's cooking in git.git (Oct 2011, #06; Tue, 18)
>>> --------------------------------------------------
>> [...]
>>> * ph/transport-with-gitfile (2011-10-11) 5 commits
>>>  (merged to 'next' on 2011-10-12 at 6d58417)
>>>  + Fix is_gitfile() for files too small or larger than PATH_MAX to be a gitfile
>>>  (merged to 'next' on 2011-10-06 at 891b8b6)
>>>  + Add test showing git-fetch groks gitfiles
>>>  + Teach transport about the gitfile mechanism
>>>  + Learn to handle gitfiles in enter_repo
>>>  + enter_repo: do not modify input
>>>
>>> Will merge to 'master' in the fifth wave.
>>
>> Do you want a re-roll of this with your is_bundle() changes added in?
>> I do like them better.
>
> Hmm, you may be right. I'll try to queue an update on top of the series
> and see what happens.

Actually there is nothing that needs re-rolling. We can just make the jc/unseekable-bundle topic graduate at the same time as this one, and let the merge remove the is_gitfile() helper that becomes unnecessary.