threads / rfc / 37522

RFC patch, 2 partsAdd documentation for sequence.format

Subject: [PATCH/RFC 2/2] Add documentation for sequence.format

## tl;dr

One message between Sep 5, 2014 and Sep 5, 2014. Diffs are folded; open one to read it.

replies: 0people: 1as markdown or json

William Clifford· Sep 5, 2014, 08:41 UTC · lore
Explain sequence.format and GIT_SEQUENCE_FORMAT.
Signed-off-by: William Clifford <mr.william.clifford@gmail.com>
Signed-off-by: Matthew Boeh <m@mboeh.com>
---
 Documentation/config.txt | 9 +++++++++
 1 file changed, 9 insertions(+)
Show changes to Documentation/config.txt +9 −0
diff --git a/Documentation/config.txt b/Documentation/config.txt
index e61775e..76f0a4d 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -555,6 +555,15 @@ sequence.editor::
 	It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable.
 	When not configured the default commit message editor is used instead.
 
+sequence.format::
+	Format of commit table generated by `git rebase -i` for rebase
+	instruction file. It can be overridden by the
+	`GIT_SEQUENCE_FORMAT` environment variable. When not
+	configured the default `oneline` format is used instead. NOTE:
+	Because the second column must be the hash, you may omit this
+	in the format string and it will be inserted. Formats must be
+	one line.
+
 core.pager::
 	Text viewer for use by Git commands (e.g., 'less').  The value
 	is meant to be interpreted by the shell.  The order of preference
-- 
William Clifford

← back to recent threads