git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Duy Nguyen <pclouds@gmail.com>
Date
Jan 14, 2013, 01:13 UTC
Message-ID
<CACsJy8CJqOcjjx5UB3w4iCC-3bmtg3oz6ieQNH5o4EGAesbO5w@mail.gmail.com>
In-Reply-To
<7vobgsheko.fsf@alter.siamese.dyndns.org>
On Mon, Jan 14, 2013 at 6:02 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 21 quoted lines
> 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).
No problem. Just tell me when you want me to flood git@vger again.
-- 
Duy
Previous: Junio C Hamano
Message 4 of 4 in “What's cooking in git.git (Jan 2013, #05; Fri, 11)”
  1. Junio C HamanoJan 11, 2013
  2. Duy NguyenJan 12, 2013
  3. Junio C HamanoJan 13, 2013
  4. Duy NguyenJan 14, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.