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

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

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

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:55:44

Duy Nguyen [off-list ref] writes:
On Sat, Jan 12, 2013 at 6:56 AM, Junio C Hamano [off-list ref] wrote:
quoted
* 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).

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

From: Duy Nguyen <hidden>
Date: 2016-06-15 22:55:44

On Mon, Jan 14, 2013 at 6:02 AM, Junio C Hamano [off-list ref] wrote:
Duy Nguyen [off-list ref] writes:
quoted
On Sat, Jan 12, 2013 at 6:56 AM, Junio C Hamano [off-list ref] wrote:
quoted
* 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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help