From: Andreas Schwab <schwab@linux-m68k.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Dan Nicolaescu <dann@ics.uci.edu>, 5211@emacsbugs.donarmstrong.com
Subject: bug#5211: Color escape codes in the output of vc-git-print-log
Date: Tue, 15 Dec 2009 19:32:25 +0100 [thread overview]
Message-ID: <m2fx7culza.fsf@igel.home> (raw)
In-Reply-To: <f7ccd24b0912150742m11ea761cg487e360d308ba29c@mail.gmail.com> (Juanma Barranquero's message of "Tue, 15 Dec 2009 16:42:45 +0100")
Juanma Barranquero <lekktu@gmail.com> writes:
> Good question. According to the logs, in July 2006
>
>
> commit fef88bb0134dfd47b4bd17e668bbb860588dcb39
> Author: Junio C Hamano <junkio@cox.net>
> Date: 2006-07-07 05:27:24 -0700
>
> diff.c: --no-color to defeat diff.color configuration.
>
> Signed-off-by: Junio C Hamano <junkio@cox.net>
>
>
> which means, if I'm not mistaken, that it appeared in git 1.4.2.
$ git describe fef88bb0134dfd47b4bd17e668bbb860588dcb39
v1.4.1-91-gfef88bb
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-12-15 18:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f7ccd24b0912271847j7f282733y358910002b582b49@mail.gmail.com>
2009-12-14 16:12 ` bug#5211: Color escape codes in the output of vc-git-print-log Juanma Barranquero
2009-12-15 4:27 ` Stefan Monnier
2009-12-15 4:31 ` Juanma Barranquero
2009-12-15 5:36 ` Eli Zaretskii
2009-12-15 11:15 ` Juanma Barranquero
2009-12-15 13:01 ` Eli Zaretskii
2009-12-15 13:09 ` Juanma Barranquero
2009-12-15 14:57 ` Dan Nicolaescu
2009-12-15 15:42 ` Juanma Barranquero
2009-12-15 18:32 ` Andreas Schwab [this message]
2009-12-15 18:36 ` Juanma Barranquero
2009-12-15 23:34 ` Andreas Schwab
2009-12-15 23:57 ` Juanma Barranquero
2009-12-28 2:49 ` bug#5211: marked as done (Color escape codes in the output of vc-git-print-log) Emacs bug Tracking System
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=m2fx7culza.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=5211@emacsbugs.donarmstrong.com \
--cc=dann@ics.uci.edu \
--cc=lekktu@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.