From: Junio C Hamano <gitster@pobox.com>
To: Phil Hord <phil.hord@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2011, #06; Tue, 18)
Date: Tue, 18 Oct 2011 09:53:25 -0700 [thread overview]
Message-ID: <7vmxcygs1m.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CABURp0po3C9-a4_cGm8gq71=gq2ELzHWBK0y7H=OEcY1=DUdsw@mail.gmail.com> (Phil Hord's message of "Tue, 18 Oct 2011 10:09:17 -0400")
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.
Thanks.
next prev parent reply other threads:[~2011-10-18 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 7:50 What's cooking in git.git (Oct 2011, #06; Tue, 18) Junio C Hamano
2011-10-18 14:09 ` Phil Hord
2011-10-18 16:53 ` Junio C Hamano [this message]
2011-10-18 18:09 ` Junio C Hamano
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=7vmxcygs1m.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=phil.hord@gmail.com \
/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