Re: [PATCH] merge-recursive: do not report the resulting tree object name

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jan 13, 2007, 11:01 UTC
Message-ID: <Pine.LNX.4.63.0701131159510.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <eo9apg$sqo$1@sea.gmane.org>

Hi,

On Sat, 13 Jan 2007, Jakub Narebski wrote:

Show 6 quoted lines

> Junio C Hamano wrote:
> 
> > I do not think we need to show 1..15 at all, perhaps without
> > "export GIT_MERGE_BASE_DEBUG=YesPlease".
> 
> Or a -v/--verbose (or even -v -v -v) flag set.

... and you'd pass them from git-pull to git-merge to git-merge-recursive? Three different programs parse the same option? And worse, the other strategies ignore the setting? What about strategies people implemented on _their_ side, which do not know about the "-v" flag? I don't think so.

Ciao, Dscho

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