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

[PATCH 1/3] doc: replay: mention no output on conflicts

From
Kkristofferhaugsbakk@fastmail.com <kristofferhaugsbakk@fastmail.com>
Date
Dec 7, 2025, 17:55 UTC
Message-ID
<no_output_on_conflict.102@msgid.xyz>
In-Reply-To
<CV_replay_conflict.101@msgid.xyz>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>

Some commands will produce output on stderr if there are conflicts, but git-replay(1) is completely silent. Explicitly spell that out.

Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
 Documentation/git-replay.adoc | 4 ++++
 1 file changed, 4 insertions(+)
diff --git a/Documentation/git-replay.adoc b/Documentation/git-replay.adoc
index dcb26e8a8e8..6fbb527b9d8 100644
--- a/Documentation/git-replay.adoc
+++ b/Documentation/git-replay.adoc
@@ -81,6 +81,10 @@ the shape of the history being replayed.  When using `--advance`, the
 number of refs updated is always one, but for `--onto`, it can be one
 or more (rebasing multiple branches simultaneously is supported).
 
+There is no stderr output on conflicts; see the <<exit-status,EXIT
+STATUS>> section below.
+
+[[exit-status]]
 EXIT STATUS
 -----------
 
-- 
2.52.0.10.g08704017180
Previous: kristofferhaugsbakk@fastmail.comNext: kristofferhaugsbakk@fastmail.com
Message 2 of 28 in “doc: replay: improvements like "mention no output on conflicts"”
  1. 0/3 doc: replay: improvements like "mention no output on conflicts"kristofferhaugsbakk@fastmail.com, Dec 7, 2025
  2. 1/3 doc: replay: mention no output on conflictskristofferhaugsbakk@fastmail.com, Dec 7, 2025
  3. 2/3 doc: replay: document --containedkristofferhaugsbakk@fastmail.com, Dec 7, 2025
  4. 3/3 doc: replay: link section using markupkristofferhaugsbakk@fastmail.com, Dec 7, 2025
  5. Junio C HamanoDec 7, 2025
  6. Kristoffer HaugsbakkDec 8, 2025
  7. Junio C HamanoDec 8, 2025
  8. Kristoffer HaugsbakkDec 9, 2025
  9. Junio C HamanoDec 9, 2025
  10. Toon ClaesDec 8, 2025
  11. Kristoffer HaugsbakkDec 8, 2025
  12. Phillip WoodDec 8, 2025
  13. Kristoffer HaugsbakkDec 9, 2025
  14. Junio C HamanoDec 9, 2025
  15. Phillip WoodDec 10, 2025
  16. Junio C HamanoDec 10, 2025
  17. Kristoffer HaugsbakkDec 10, 2025
  18. Phillip WoodDec 10, 2025
  19. Elijah NewrenDec 10, 2025
  20. 0/3 doc: replay: improvements like "mention no output on conflicts"kristofferhaugsbakk@fastmail.com, Dec 13, 2025
  21. 1/3 doc: replay: mention no output on conflictskristofferhaugsbakk@fastmail.com, Dec 13, 2025
  22. 2/3 replay: improve --contained and add to dockristofferhaugsbakk@fastmail.com, Dec 13, 2025
  23. 3/3 doc: replay: link section using markupkristofferhaugsbakk@fastmail.com, Dec 13, 2025
  24. Phillip WoodDec 15, 2025
  25. Kristoffer HaugsbakkDec 15, 2025
  26. Junio C HamanoDec 16, 2025
  27. Phillip WoodDec 16, 2025
  28. Kristoffer HaugsbakkDec 20, 2025

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.