From: Felipe Contreras <felipe.contreras@gmail.com>
To: Max Horn <max@quendi.de>, Felipe Contreras <felipe.contreras@gmail.com>
Cc: Jeff King <peff@peff.net>,
Andrew Ardill <andrew.ardill@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Our official home page and logo for the Git project
Date: Fri, 11 Apr 2014 13:56:00 -0500 [thread overview]
Message-ID: <53483ac0be5d5_937adb308e2@nysa.notmuch> (raw)
In-Reply-To: <40FDE1FF-780F-46E1-A5AA-57D53D6D1C87@quendi.de>
Max Horn wrote:
> On 11.04.2014, at 17:21, Felipe Contreras <felipe.contreras@gmail.com> wrote:
> > Max Horn wrote:
> >> On 11.04.2014, at 15:29, Felipe Contreras <felipe.contreras@gmail.com> wrote:
> >>> Max Horn wrote:
> >>>
> >>> You don't think red represent an oldness in Git? Whereas green
> >>> represents progress?
> >>
> >> No, I don't think that.
> >
> > Then you belong to the minority of Git users. Those of us that see
> > patches day and night, red is old, green is new.
>
> Hasty generalization.
You don't know what a hasty generalization is. If you want me to explain it to
you, send me a personal e-mail, you are polluting the discussion enough as it
is.
> Come back when you have facts, as opposed to the illusion that you are the
> spokesperson of the (apparently silent) majority of Git users.
Facts:
1) A hunk that removed (-) is represented in red [1]
2) A hunk that added (+) is represented in green [1]
3) A file that is removed is represented in red [2]
4) A file that is added or modified is represented in green [2]
5) A test that fails is represented in red [3]
6) A test that succeeds is represented in green [3]
7) The current Git logo (accordo to some people) has "-" in red, "+" in green [4]
Given these facts, it's reasonable to assume that to the majority of Git users
red is old and bad, green is new and good.
[1] http://ubuntuone.com/0lxzuxY2b59OEdDK5EOvfi
[2] http://media.smashingmagazine.com/wp-content/uploads/2011/06/git1_4_git-status.gif
[3] http://felipec.org/git-tests.png
[4] https://plus.google.com/112500102483798323902/posts
--
Felipe Contreras
next prev parent reply other threads:[~2014-04-11 19:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 18:44 Our official home page and logo for the Git project Junio C Hamano
2014-04-09 14:54 ` Matthieu Moy
2014-04-09 16:43 ` Felipe Contreras
2014-04-10 0:24 ` Andrew Ardill
2014-04-10 7:32 ` David Kastrup
2014-04-11 11:32 ` Javier Domingo Cansino
2014-04-11 16:58 ` Tim Chase
2014-04-11 11:40 ` Jeff King
2014-04-11 12:39 ` Max Horn
2014-04-11 13:29 ` Felipe Contreras
2014-04-11 15:02 ` Max Horn
2014-04-11 15:21 ` Felipe Contreras
2014-04-11 18:37 ` Max Horn
2014-04-11 18:56 ` Felipe Contreras [this message]
2014-04-11 19:24 ` Max Horn
2014-04-11 20:26 ` Felipe Contreras
2014-04-11 15:39 ` Philippe Vaucher
2014-04-11 15:48 ` Philippe Vaucher
2014-04-11 16:52 ` Holger Hellmuth
2014-04-11 17:21 ` Felipe Contreras
2014-04-11 18:35 ` Max Horn
2014-04-11 13:24 ` Felipe Contreras
2014-04-11 13:44 ` David Kastrup
2014-04-11 14:09 ` Vincent van Ravesteijn
2014-04-11 15:22 ` Felipe Contreras
2014-04-12 12:34 ` Jeff King
2014-04-12 14:02 ` Felipe Contreras
[not found] ` <CALZVapkdr5R8h3XWwmo3LHEXnMrOQhzVCw2LwP5oRbJ=MVnbUg@mail.gmail.com>
2014-04-13 8:53 ` Javier Domingo Cansino
2014-04-14 8:28 ` Stefan Beller
2014-04-20 17:53 ` Felipe Contreras
2014-04-11 19:25 ` Junio C Hamano
2014-04-11 19:38 ` Jonathan Nieder
2014-04-11 19:45 ` Ronnie Sahlberg
2014-04-11 21:25 ` Brandon McCaig
2014-04-12 4:28 ` Michael Haggerty
2014-04-12 12:05 ` Jeff King
2014-04-14 13:39 ` Erik Faye-Lund
2014-04-11 16:24 ` Michael Haggerty
2014-04-11 17:07 ` Karsten Blees
2014-04-11 17:20 ` David Kastrup
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=53483ac0be5d5_937adb308e2@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=andrew.ardill@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=max@quendi.de \
--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).