From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Alexander Kern <alex.kern@gmx.de>
Cc: James Simmons <jsimmons@infradead.org>,
fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Where is the latest work for fbdev
Date: Sat, 19 Jun 2004 23:42:18 +0200 [thread overview]
Message-ID: <20040619214218.GC20632@lug-owl.de> (raw)
In-Reply-To: <200406192227.47534.alex.kern@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
On Sat, 2004-06-19 22:27:47 +0200, Alexander Kern <alex.kern@gmx.de>
wrote in message <200406192227.47534.alex.kern@gmx.de>:
> What about submitting to mainline
>
> <[Linux-fbdev-devel] Newest fbdev patch to go mainline.
> <(James Simmons, Kopie: Linux Kernel Mailing List, Tue Feb 10 07:36:03 2004)
>
> Today is 19 Jun!
James has to do quite a lot of work, and submitting patches is one of
the "boring" jobs that suffer from that. Actually, we have in common to
think that {a,some} people that work only on patch submission would be a
quite cool thing, but that's hard to achieve given a full-time day job
plus overtime work :( That has just been discussed on LKML...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-19 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 20:27 Where is the latest work for fbdev Alexander Kern
2004-06-19 21:42 ` Jan-Benedict Glaw [this message]
2004-06-23 18:35 ` jsimmons
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=20040619214218.GC20632@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=alex.kern@gmx.de \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).