git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] rm: resolving by removal is not a warning-worthy event

From
Jeff King <peff@peff.net>
Date
Jul 18, 2019, 21:43 UTC
Message-ID
<20190718214325.GA28619@sigill.intra.peff.net>
In-Reply-To
<xmqq8ssvxd9w.fsf@gitster-ct.c.googlers.com>
On Thu, Jul 18, 2019 at 02:07:23PM -0700, Junio C Hamano wrote:
Show 11 quoted lines
> >> +	git rm qfwfq >msg &&
> >> +	test_i18ngrep ! "needs merge" msg &&
> >
> > Should we capture stderr from "git rm", too, to cover all bases?
> 
> Do you mean
> 
> 	git rm blob >msg 2>&1
> 
> because we could later change our mind and send "needs merge"
> message to the standard error stream?
Yes, exactly.
-Peff
Previous: Junio C Hamano
Message 6 of 6 in “Merge: "git rm bla": "bla: needs merge", but still removes file "bla"”
  1. Ulrich WindlJul 17, 2019
  2. Junio C HamanoJul 17, 2019
  3. rm: resolving by removal is not a warning-worthy eventJunio C Hamano, Jul 17, 2019
  4. Jeff KingJul 18, 2019
  5. Junio C HamanoJul 18, 2019
  6. Jeff KingJul 18, 2019

Read the whole thread, see it on lore, or plain text.

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