Re: [BUG] "git pull" will regress between 'master' and 'pu'

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 20, 2015, 19:28 UTC
Message-ID: <xmqq8udmlhu0.fsf@gitster.dls.corp.google.com>
In-Reply-To: <xmqqbnikoq0n.fsf@gitster.dls.corp.google.com>

Junio C Hamano <gitster@pobox.com> writes:

Show 7 quoted lines

> 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.

Thanks.

$ 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.