linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: James Simmons <jsimmons@transvirtual.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Linux 2.5.19
Date: Thu, 30 May 2002 00:42:09 +0200	[thread overview]
Message-ID: <3CF55941.7060806@evision-ventures.com> (raw)
In-Reply-To: 20020530002559.G30585@flint.arm.linux.org.uk

Russell King wrote:

> What if I were to take, say, Mochel's experimental tree and send some
> random alpha code to Linus?  Let anarchy rule!

Well ... they have once excuse... if the maintainer is
himself a bit slow on submitting to Linus. Yes I know that's
a matter primary of personal style so there is no need
to discuss about it until down...

About the anarchy - are you sure a Kozaks blood like me
couldn't life up with it ruling? :-).


_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

  reply	other threads:[~2002-05-29 23:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020529211702.E30585@flint.arm.linux.org.uk>
2002-05-29 20:44 ` Linux 2.5.19 James Simmons
2002-05-29 20:47   ` Russell King
2002-05-29 22:22     ` Martin Dalecki
2002-05-29 23:25       ` Russell King
2002-05-29 22:42         ` Martin Dalecki [this message]
2002-05-29 23:52           ` Russell King
2002-05-29 23:00             ` Martin Dalecki
2002-05-29 22:43     ` James Simmons
2002-05-29 22:29       ` Martin Dalecki
2002-05-29 23:31         ` Russell King
2002-05-30  5:10           ` Framebuffer policy [ was Re: Linux 2.5.19] James Simmons

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=3CF55941.7060806@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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).