ryenusIt would help especially when the commit message was written badly.
Or it might be possible to customize just like "git log --format"?
Thanks
threads / discuss / 44402
[git rebase -i] show time and author besides commit hash and message?
Subject: [git rebase -i] show time and author besides commit hash and message?
ryenus
Alexei LozovskyRe: [git rebase -i] show time and author besides commit hash and message?
> It would help especially when the commit message was written badly. > > Or it might be possible to customize just like "git log --format"?
It is possible to change the format globally via config option rebase.instructionFormat:
$ git config rebase.instructionFormat "%an (%ad): %s"
The format is the same as for 'git log'. This one outputs author name, date, and the first line of commit message.
This option is supported since Git 2.6.
Or are you interested in a command-line option that can change the format on per-invocation basis? I think there isn't one. It can be interesting to add it, but I don't think it has much utility...
Jeff King[PATCH] doc: fix missing "::" in config list
On Sun, Oct 30, 2016 at 07:21:41PM +0200, Alexei Lozovsky wrote:
Show 8 quoted lines
> > It would help especially when the commit message was written badly. > > > > Or it might be possible to customize just like "git log --format"? > > It is possible to change the format globally via config option > rebase.instructionFormat: > > $ git config rebase.instructionFormat "%an (%ad): %s"
I had totally forgotten we added this option. When I went to look at its documentation, I found the formatting a bit funny. This should fix it.
-- >8 -- Subject: [PATCH] doc: fix missing "::" in config list
The rebase.instructionFormat option is missing its "::" to tell AsciiDoc that it's a list entry. As a result, the option name gets lumped into the description in one big paragraph.
Signed-off-by: Jeff King <peff@peff.net> --- Documentation/config.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt index 27069ac03..a0ab66aae 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -2450,7 +2450,7 @@ rebase.missingCommitsCheck:: command in the todo-list. Defaults to "ignore". -rebase.instructionFormat +rebase.instructionFormat:: A format string, as specified in linkgit:git-log[1], to be used for the instruction list during an interactive rebase. The format will automatically have the long commit hash prepended to the format.
-- 2.10.2.870.g7471999
ryenusRe: [git rebase -i] show time and author besides commit hash and message?
Show 7 quoted lines
> It is possible to change the format globally via config option > rebase.instructionFormat: > > $ git config rebase.instructionFormat "%an (%ad): %s" > > The format is the same as for 'git log'. This one outputs author > name, date, and the first line of commit message.
Thanks for the prompt response! I tried immediately, it works just as you have pointed out.
Just it seems coloring is not supported? probably because we're inside an editor?
> This option is supported since Git 2.6.
I missed it, what about including a note about this option as part of the comment in git rebase -i? since that's the place where people would most likely think about it?
> Or are you interested in a command-line option that can change > the format on per-invocation basis? I think there isn't one. > It can be interesting to add it, but I don't think it has much > utility...
Not much, for git log I'd rather setup an alias "git la", than having to remember various fields, colors, padding options to have a nice output.
Jeff KingRe: [git rebase -i] show time and author besides commit hash and message?
On Mon, Oct 31, 2016 at 11:27:33PM +0800, ryenus wrote:
Show 13 quoted lines
> > It is possible to change the format globally via config option > > rebase.instructionFormat: > > > > $ git config rebase.instructionFormat "%an (%ad): %s" > > > > The format is the same as for 'git log'. This one outputs author > > name, date, and the first line of commit message. > > Thanks for the prompt response! > I tried immediately, it works just as you have pointed out. > > Just it seems coloring is not supported? probably because > we're inside an editor?
Yes. If git outputs its own ANSI codes there, they generally look bad in an editor (interpreted as raw bytes, not as coloring). Any existing coloring you see is likely due to syntax highlighting done by your editor. You can extend that to match your desired format, but exactly how would depend on which editor you're using.
-Peff