linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: board/device file names, and machine names
Date: Wed, 3 Mar 2010 10:08:47 +0000	[thread overview]
Message-ID: <20100303100847.GA30607@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100303100022.GA7175@atrey.karlin.mff.cuni.cz>

On Wed, Mar 03, 2010 at 11:00:23AM +0100, Pavel Machek wrote:
> 
> > On Wed, Mar 03, 2010 at 10:17:28AM +0100, Pavel Machek wrote:
> > > Hi!
> > > 
> > > > > However, we need some future direction ..
> > > > 
> > > > Given the amount of discussion there's already been, I'm going to come
> > > > down hard on this issue to kill the discussion.
> > > > 
> > > > Stick with Google's existing naming for files and interally within files.
> > > > Put a comment in the files giving all the names.  Use the common name in
> > > > the Kconfig text, and either put the internal names in the help text or
> > > > in brackets in the main option text.
> > > > 
> > > > 
> > > > Don't like it?  I'm sure there's always going to be someone who doesn't
> > > > like whatever is decided upon, so get over it.  The important thing is
> > > > that the decision is made, and that there's no further dithering over
> > > > this issue.
> > > 
> > > Does not seem to be your decision. At least you should have cc-ed l-k.
> > 
> > You really need to get a life.
> 
> And you really need to start to behave.

No Pavel, it is YOU who need to behave.  You also need to go back to
school to learn to read.

> So... dwalker is maintainer of arch-msm, and does not like the
> codenames. Then you come, and just because are maintainer of arm,
> override the decision, without even notifying l-k?

So you don't think that Daniel, who was *explicitly* asking for my
suggestions and opinions, is entitled to a clear and straight answer?

Yes, go back and read the fucking thread properly Pavel.  Daniel
explicitly sent his messages TO me and ASKED me for this.

Daniel had my suggestions on my first reply in this thread, and his
follow up to that indicated he wanted something firmer - he wanted
a decision _FROM ME_ on which way to go.  That's precisely what he
got.

What you're actually trying to say is that you don't like me and you
certainly don't like me making any kind of decision.  Get over it, or
find some other project to infiltrate and infest with your idiotic
attitude.

  reply	other threads:[~2010-03-03 10:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 21:29 board/device file names, and machine names Daniel Walker
2010-03-02 22:56 ` Brian Swetland
2010-03-02 23:29   ` Daniel Walker
2010-03-02 23:38     ` Brian Swetland
2010-03-03  3:42     ` Bill Gatliff
2010-03-03  3:36   ` Bill Gatliff
2010-03-03  8:00     ` Brian Swetland
2010-03-03 19:08   ` Theodore Tso
2010-03-03 19:22     ` Theodore Tso
2010-03-03 19:24     ` Russell King - ARM Linux
2010-03-02 23:51 ` Russell King - ARM Linux
2010-03-03  0:39   ` Daniel Walker
2010-03-03  0:47     ` Tim Bird
2010-03-03  0:52       ` Daniel Walker
2010-03-03  1:01         ` Brian Swetland
2010-03-03  3:52     ` Bill Gatliff
2010-03-03  8:42     ` Russell King - ARM Linux
2010-03-03  9:17       ` Pavel Machek
2010-03-03  9:47         ` Russell King - ARM Linux
2010-03-03 10:00           ` Pavel Machek
2010-03-03 10:08             ` Russell King - ARM Linux [this message]
2010-03-03 10:18               ` Pavel Machek
2010-03-03 10:19                 ` Russell King - ARM Linux
2010-03-03 14:24                   ` Pavel Machek
2010-03-03 14:38       ` Daniel Walker
2010-03-03 22:08   ` Nicolas Pitre
2010-03-03 22:27     ` Brian Swetland
2010-03-03  3:25 ` Bill Gatliff

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=20100303100847.GA30607@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).