unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 5211@emacsbugs.donarmstrong.com
Subject: bug#5211: Color escape codes in the output of vc-git-print-log
Date: Wed, 16 Dec 2009 00:57:54 +0100	[thread overview]
Message-ID: <f7ccd24b0912151557o44c80098m67afa6709aad8d9@mail.gmail.com> (raw)
In-Reply-To: <m2r5qvu7z2.fsf@igel.home>

On Wed, Dec 16, 2009 at 00:34, Andreas Schwab <schwab@linux-m68k.org> wrote:

> That just means the commit is 91 commits after tag v1.4.1, and there is
> no other tag in between.

OK, thanks.

> $ git tag --contains fef88bb0134dfd47b4bd17e668bbb860588dcb39 | head -1
> v1.4.2

So --no-color was first included in a release of 2006-08-13. Is that
old enough? (git 1.0.0 is from 2005-12-21, barely eight months
earlier, so 1.4.2 is quite old indeed).

    Juanma





  reply	other threads:[~2009-12-15 23:57 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
2009-12-15 18:36         ` Juanma Barranquero
2009-12-15 23:34           ` Andreas Schwab
2009-12-15 23:57             ` Juanma Barranquero [this message]
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=f7ccd24b0912151557o44c80098m67afa6709aad8d9@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=5211@emacsbugs.donarmstrong.com \
    --cc=schwab@linux-m68k.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).