git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: ryenus <ryenus@gmail.com>
Cc: Alexei Lozovsky <a.lozovsky@gmail.com>,
	Git mailing list <git@vger.kernel.org>
Subject: Re: [git rebase -i] show time and author besides commit hash and message?
Date: Mon, 31 Oct 2016 11:57:09 -0400	[thread overview]
Message-ID: <20161031155709.nimnuucq75kn6mau@sigill.intra.peff.net> (raw)
In-Reply-To: <CAKkAvay4YuRuGhub6W308+DmrZtrO3+NWu8NvfB--Mb9Z59Xzw@mail.gmail.com>

On Mon, Oct 31, 2016 at 11:27:33PM +0800, ryenus wrote:

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

      reply	other threads:[~2016-10-31 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-30 17:03 [git rebase -i] show time and author besides commit hash and message? ryenus
2016-10-30 17:21 ` Alexei Lozovsky
2016-10-30 18:46   ` [PATCH] doc: fix missing "::" in config list Jeff King
2016-10-31 15:27   ` [git rebase -i] show time and author besides commit hash and message? ryenus
2016-10-31 15:57     ` Jeff King [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161031155709.nimnuucq75kn6mau@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=a.lozovsky@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ryenus@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).