git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Jeff King <peff@peff.net>, Nanako Shiraishi <nanako3@lavabit.com>
Subject: Re: [PATCH] graph API: Added logic for colored edges
Date: Wed, 08 Apr 2009 17:29:31 -0700	[thread overview]
Message-ID: <7vocv6is9g.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090408214129.GA20764@linux.vnet> (Allan Caffee's message of "Wed, 8 Apr 2009 17:41:29 -0400")

Allan Caffee <allan.caffee@gmail.com> writes:

> The problem with making it an index into the column_colors array is that
> we don't have a convenient place to test whether the user actually wants
> color.  We can't do it in strbuf_write_column because AFAIK there's no
> way to get the rev-info to test the options.  I suppose we could define
> GIT_NOT_A_COLOR to -1 and just set the color to that when we don't
> intend to use color.  (Either way I should probably change that to an
> unsigned short.)  What do you think?

Sounds sensible.

  reply	other threads:[~2009-04-09  0:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090331235922.GA7411@linux.vnet>
2009-04-07 18:57 ` [PATCH] graph API: Added logic for colored edges Allan Caffee
2009-04-08  7:59   ` Junio C Hamano
2009-04-08 21:41     ` Allan Caffee
2009-04-09  0:29       ` Junio C Hamano [this message]
2009-04-09 22:22         ` [PATCH v3] " Allan Caffee
2009-04-12  8:44           ` Junio C Hamano
2009-04-12 17:43             ` Allan Caffee
2009-04-12 18:45               ` Junio C Hamano
2009-04-12 20:27                 ` [PATCH v4] " Allan Caffee
2009-04-12 21:59                   ` Junio C Hamano
2009-04-13 19:53                     ` [PATCH v5] " Allan Caffee
2009-04-09 17:58   ` [PATCH] " Teemu Likonen
2009-04-09 22:08     ` Allan Caffee

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=7vocv6is9g.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=nanako3@lavabit.com \
    --cc=peff@peff.net \
    /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).