From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2013, #05; Fri, 11)
Date: Sun, 13 Jan 2013 15:02:15 -0800 [thread overview]
Message-ID: <7vobgsheko.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CACsJy8CRbkLAD7LtoE_6FA_zW4YTW6Nb0mJU3ejqbu5URTrU1Q@mail.gmail.com> (Duy Nguyen's message of "Sat, 12 Jan 2013 23:25:45 +0700")
Duy Nguyen <pclouds@gmail.com> writes:
> On Sat, Jan 12, 2013 at 6:56 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> * nd/parse-pathspec (2013-01-11) 20 commits
>>
>> Uses the parsed pathspec structure in more places where we used to
>> use the raw "array of strings" pathspec.
>>
>> Unfortunately, this conflicts a couple of topics in flight. I tried
>> to be careful while resolving conflicts, though.
>
> parse_pathspec has not picked up init_pathspec changes from
> jk/pathspec-literal and nd/pathspec-wildcard (already in master) so
> --literal-pathspecs is probably broken in 'pu' after a lot of
> init_pathspec -> parse_pathspec conversion.
I guess it may be a better way forward to hold the series off, and
instead help polishing the other topics that are depended on so that
they can graduate sooner, given multiple topics in flight wants to
touch pathspecs (either change the way they are handled, or adds new
places that use them).
next prev parent reply other threads:[~2013-01-13 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 23:56 What's cooking in git.git (Jan 2013, #05; Fri, 11) Junio C Hamano
2013-01-12 16:25 ` Duy Nguyen
2013-01-13 23:02 ` Junio C Hamano [this message]
2013-01-14 1:13 ` Duy Nguyen
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=7vobgsheko.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@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