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

[PATCH] sequencer: use configured comment character

From
Aaron Schrab <aaron@schrab.com>
Date
Jun 28, 2018, 02:04 UTC
Message-ID
<20180628020414.25036-1-aaron@schrab.com>

Use configured comment character when generating comments about branches in an instruction sheet. Failure to honor this configuration causes a failure to parse the resulting instruction sheet.

Signed-off-by: Aaron Schrab <aaron@schrab.com>
---
 sequencer.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sequencer.c b/sequencer.c
index 4034c0461b..caf91af29d 100644
--- a/sequencer.c
+++ b/sequencer.c
@@ -3991,7 +3991,7 @@ static int make_script_with_merges(struct pretty_print_context *pp,
 		entry = oidmap_get(&state.commit2label, &commit->object.oid);
 
 		if (entry)
-			fprintf(out, "\n# Branch %s\n", entry->string);
+			fprintf(out, "\n%c Branch %s\n", comment_line_char, entry->string);
 		else
 			fprintf(out, "\n");
 
-- 
2.18.0.419.gfe4b301394
Next: Johannes Schindelin
Message 1 of 5 in “sequencer: use configured comment character”
  1. sequencer: use configured comment characterAaron Schrab, Jun 28, 2018
  2. Johannes SchindelinJun 28, 2018
  3. Junio C HamanoJun 28, 2018
  4. Johannes SchindelinJun 29, 2018
  5. Junio C HamanoJun 29, 2018

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.