Re: [BUG] "git pull" will regress between 'master' and 'pu'
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Apr 21, 2015, 07:23 UTC
- Message-ID
- <84c2d3dcb754d14a9f43deb7bbb6fd79@www.dscho.org>
- In-Reply-To
- <xmqq8udmlhu0.fsf@gitster.dls.corp.google.com>
Hi Junio,
On 2015-04-20 21:28, Junio C Hamano wrote:
Show 15 quoted lines
> Junio C Hamano <gitster@pobox.com> writes: > >> This is primarily note-to-self; even though I haven't got around >> bisecting yet, I think I know I did some bad change myself. >> >> "git pull $URL $tag" seems to: >> >> * fail to invoke the editor without "--edit". >> * show the summary merge log message twice. > > We seem to be making a good progress on the discussion on this > specific issue, but a larger tangent of this is that we do not seem > to have test coverage to catch this regression. As we are planning > to rewrite "git pull", we need to make sure we have enough test > coverage to ensure that nothing will regress before doing so.
Yes, the plan is to use code coverage tools to ensure that a decent amount of code paths/parameters is covered.
Ciao, Dscho