Re: What's cooking in git.git (Jun 2016, #04; Tue, 14)
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 15, 2016, 18:32 UTC
- Message-ID
- <xmqqd1ni716g.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <20160615023658.GA21270@glandium.org>
Mike Hommey <mh@glandium.org> writes:
> On Tue, Jun 14, 2016 at 03:08:04PM -0700, Junio C Hamano wrote:
Show 9 quoted lines
>> * mh/connect (2016-06-06) 10 commits >> - connect: [host:port] is legacy for ssh >> ... >> - connect: document why we sometimes call get_port after get_host_and_port >> >> Ok, folks, is everybody happy with this version? > > $gmane/296609 > $gmane/296610
Oh, I have seen these, and I know you two are happy.
But I am having a hard time coming up with a few-line summary for this topic. I can write the beginning part, i.e. "Git-URL parsing routine has been rewritten", but the concluding part of the sentence cannot be "... has been rewritten for no good reason." if I were to mark the topic as "Will merge to 'next'". The best I can come up with is "... has been rewritten (hopefully) without changing the benaviour.", but that is not a strong-enough justificaiton to make the change to the codebase, either.
In short, while the update may not introduce new bugs, why would we want to have this change in the first place?
By the way, please do not quote the whole thing when you are responding to a tiny part of the original message.