All of lore.kernel.org
 help / color / mirror / Atom feed
From: yanhua <yanh@lemote.com>
To: zhangfx@lemote.com, gnewsense-dev@nongnu.org,
	linux-mips@linux-mips.org, loongson@bjlx.org.cn, yanh@lemote.com
Subject: Re: yeloong or yeeloong
Date: Wed, 01 Apr 2009 09:46:38 +0800	[thread overview]
Message-ID: <49D2C77E.4090105@lemote.com> (raw)
In-Reply-To: <20090331175252.GB4918@adriano.hkcable.com.hk>

There are really yeloong and yeeloong fix using. That is a mistake. Now 
I have all of them changed to yeeloong for consistency. The latest is 
already in our git repos.

Zhang Le 写道:
> Sorry for cross posting, but I just want to bring this issue to a wider
> audience.
>
> Maybe I am not the one who should be worried about this. But since more and
> more people will get these machines, we should settle it down as early as
> possible.
>
> This is a bikeshedding problem[1], so _everyone_ is welcome to comment.
>
> First of all, this problem is first discovered by Liu Shiwei, the manager of
> Beijing Loongson Club. If you search 'yeloong', this post will appear in the
> first page:
> http://www.lemote.com/bbs/redirect.php?tid=21768&goto=lastpost
>
> Then, I have proposed a naming convention change to lemote. That was a patch
> which I didn't post it to a public mailing list. But you can get it here:
> http://repo.or.cz/w/linux-2.6/linux-loongson.git?a=shortlog;h=refs/heads/lemote-naming-convention
> In that patch, I sugguest keep fuloong, but call the notebook yeeloong instead
> of yeloong.
>
> The following are the rationales behind my suggestions:
>
>   1. Fulong -> Fuloong.
>
>     This one is good. For those who has a box, please cat your /proc/cpuinfo.
>     It should still be fulong. And I believe the fulong should be a typo.
>
>   2. Yeeloong -> Yeloong. 
>
>     I think this one is controversial. The e in Yeloong, to me, sounds like e
>     in yes, not ee in eel. So that the sound is changed, this action is by
>     itself bad. And Yeloong may make people connect it with the word yell,
>     which is not quite good a word. Moreover, the original sound is more like 
>     its Chinese brand name.
>
> And, recently I have just noticed that at the long long last lemote is going
> to push Loongson 2F patches to upstream, which is good. However, I found the
> notebook's name is still yeloong:
> http://dev.lemote.com/git?p=linux_loongson.git;a=shortlog;h=refs/heads/to-mips
>
> So, I hope lemote could seriously take my suggestion in consideration. And if my
> suggestion were rejected, please give your reason behind the rejection.
>
> Thanks for everyone's time!
>
> Zhang, Le
> http://zhangle.is-a-geek.org
>
> [1] http://en.wikipedia.org/wiki/Color_of_the_bikeshed
>
>   


-- 
晏华

  parent reply	other threads:[~2009-04-01  1:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15359.159.226.43.42.1238459390.squirrel@mail.lemote.com>
2009-03-31 17:52 ` yeloong or yeeloong Zhang Le
2009-04-01  0:34   ` yanhua
2009-04-01  1:46   ` yanhua [this message]
2009-04-01  4:19   ` fxzhang
2009-04-01  9:30     ` Zhang Le
2009-04-01  9:16   ` Kevin D. Kissell

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=49D2C77E.4090105@lemote.com \
    --to=yanh@lemote.com \
    --cc=gnewsense-dev@nongnu.org \
    --cc=linux-mips@linux-mips.org \
    --cc=loongson@bjlx.org.cn \
    --cc=zhangfx@lemote.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.