git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Felipe Contreras <felipe.contreras@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: Our official home page and logo for the Git project
Date: Fri, 11 Apr 2014 18:24:34 +0200	[thread overview]
Message-ID: <53481742.4090304@alum.mit.edu> (raw)
In-Reply-To: <534578b2e22e2_af197d3081@nysa.notmuch>

On 04/09/2014 06:43 PM, Felipe Contreras wrote:
> Junio C Hamano wrote:
>>  - To officially adopt the logo that appears on the "project
>>    home page" as our "project logo".
> 
> I have made my objections to that logo before, but here it goes again: bright
> red is a horrible color for a logo, as it only looks good in limited
> situations. I propose you use the logo I chose for git-fc[1] which has a better
> color, and instead of showing commits going down, they go up.

That's funny; I think that commits *already* go up in the red logo,
because what is represented is a merge, not a branch.

Robust and easy merging, after all, was one of Git's early claims to fame.

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/

  parent reply	other threads:[~2014-04-11 16:24 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
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 [this message]
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=53481742.4090304@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
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).