From: Junio C Hamano <gitster@pobox.com>
To: markus.heidelberg@web.de
Cc: Stephen Boyd <bebarino@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] show-branch: color the commit status signs
Date: Wed, 22 Apr 2009 14:16:25 -0700 [thread overview]
Message-ID: <7vskk01j9y.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200904222245.24034.markus.heidelberg@web.de> (Markus Heidelberg's message of "Wed, 22 Apr 2009 22:45:23 +0200")
Markus Heidelberg <markus.heidelberg@web.de> writes:
> Stephen Boyd, 22.04.2009:
>> On Tue, Apr 21, 2009, Markus Heidelberg <markus.heidelberg@web.de> wrote:
>> > +--color::
>> > + Color the status sign of the commits. Each branch uses a single color.
>>
>> I don't know what the status sign of a commit is without reading your commit
>> message. Maybe reword this to be:
>>
>> Color the status sign ('*' '!' '+' '-') of each commit corresponding
>> to the branch
>> it's in.
>
> I had some problems with finding the right words for the description and
> still wasn't satisfied with it. I think your suggestion makes it easier
> and will include it.
>
>> > +static char column_colors[][COLOR_MAXLEN] = {
>> > + GIT_COLOR_RED,
>> > + GIT_COLOR_GREEN,
>> > + GIT_COLOR_YELLOW,
>> > + GIT_COLOR_BLUE,
>> > + GIT_COLOR_MAGENTA,
>> > + GIT_COLOR_CYAN,
>> > +};
>> > +
>> > +#define COLUMN_COLORS_MAX (ARRAY_SIZE(column_colors))
>>
>> This looks like a copy/paste (with a small edit) from graph.c so maybe you
>> want to refactor the original code from graph.c to color.h?
>
> How exactly do you think it can be refactored and then combined?
These tables belong to each command. Your show-branches do not
necessarily want to get different set or number of colors when graph
output updates its color palette to have richer set of colors. I do not
see any need for "refactoring" here.
next prev parent reply other threads:[~2009-04-22 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 21:52 [PATCH] show-branch: color the commit status signs Markus Heidelberg
2009-04-22 19:26 ` Stephen Boyd
2009-04-22 20:45 ` Markus Heidelberg
2009-04-22 21:16 ` Junio C Hamano [this message]
2009-04-22 21:41 ` [PATCH v2] " Markus Heidelberg
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=7vskk01j9y.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=markus.heidelberg@web.de \
/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).