Re: What's cooking in git.git (Jan 2013, #05; Fri, 11)

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 13, 2013, 23:02 UTC
Message-ID: <7vobgsheko.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CACsJy8CRbkLAD7LtoE_6FA_zW4YTW6Nb0mJU3ejqbu5URTrU1Q@mail.gmail.com>

Duy Nguyen <pclouds@gmail.com> writes:

Show 13 quoted lines

> 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).