mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian Swetland <swetland@google.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Arve Hj?nnev?g" <arve@android.com>,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Daniel Walker <dwalker@codeaurora.org>,
	Iliyan Malchev <malchev@google.com>
Subject: Re: HTC Dream: dream is better name for this machine
Date: Sun, 6 Dec 2009 15:27:38 -0800	[thread overview]
Message-ID: <a55d774e0912061527t5b09b510g1fc458b53a423c04@mail.gmail.com> (raw)
In-Reply-To: <20091206205041.GA12555@elf.ucw.cz>

On Sun, Dec 6, 2009 at 12:50 PM, Pavel Machek <pavel@ucw.cz> wrote:
>
> While few people may know HTC Dream by its codename, it is better to
> use name of released hardware in the sources.

I still think that it'd be less pain for everyone to leave it as
trout.  If you go by sales volume, the most known released hardware
name is "Tmobile G1", some people know it as ADP1, and I believe it
has sold under a few other names in other markets, but the software
has, since day one, been trout and changing that just makes it harder
to merge other existing changes where we'd have to deal with renames
as well.  The bootloader identifies it as "trout", and the userspace
software stack's hardware-specific bits refer to trout.

If it really drives everyone crazy, we could do a big rename once it's
all in and working, but right now I just don't see the benefit.

Brian

  parent reply	other threads:[~2009-12-06 23:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-06 20:50 Pavel Machek
2009-12-06 20:55 ` Pavel Machek
2009-12-06 23:27 ` Brian Swetland [this message]
2009-12-07 10:07   ` Pavel Machek

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=a55d774e0912061527t5b09b510g1fc458b53a423c04@mail.gmail.com \
    --to=swetland@google.com \
    --cc=arve@android.com \
    --cc=dwalker@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malchev@google.com \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®