Re: [PATCH] pathspec: warn on empty strings as pathspec

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Emily Xie <emilyxxie@xxxxxxxxx> writes:

> Awesome. Thanks, Junio---this is exciting!

No, thank _you_.

> As for step 2: do you have a good sense on the timing? Around how long
> should I wait to submit the patch for it?

Not so fast.  We'll wait for others to comment first.

I am queuing this change but that does not mean anything more than
that I am not outright rejecting the idea.

It is possible that others may assess the cost of having to do the
two-step migration differently, and the list concensus may end up
being "if it hurts, don't pass an empty string", i.e. we'd better
without this patch or subsequent second step.  If that happens, the
first step dies without hitting 'next'.  I'd say we'd wait at least
for a week.

Otherwise, if the change is received favourably, we'll merge it to
'next', do the same waiting for comments.  Repeat the same and then
merge to 'master'.  After it hits the next feature release (probably
at around the end of August), the change will be seen by wider
general public, and at that point we may see strong opposition from
them with a good argument neither of us thought of why we shouldn't
do this change, in which case we might have to revise the plan and
scrap the whole thing.

So, we'll wait and see.

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]