linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: jsimmons@pentafluge.infradead.org
Cc: adaplas@pol.net, eger@havoc.gtf.org,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH][RIVAFB]: Updates to rivafb driver
Date: Wed, 16 Jun 2004 13:23:18 -0700	[thread overview]
Message-ID: <20040616132318.1435b0c7.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.56.0406161743100.14901@pentafluge.infradead.org>

jsimmons@pentafluge.infradead.org wrote:
>
> Nice. I will apply.

And then what will happen?

Patches seem to disappear into the linux-fbdev tree never to be seen again.
What can we do about this?


-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND

  reply	other threads:[~2004-06-16 20:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15 20:06 [PATCH][RIVAFB]: Updates to rivafb driver Antonino A. Daplas
2004-06-15 22:17 ` David Eger
2004-06-15 22:18   ` jsimmons
2004-06-16  2:44   ` Antonino A. Daplas
2004-06-16  5:53     ` Antonino A. Daplas
2004-06-16 16:47       ` jsimmons
2004-06-16 20:23         ` Andrew Morton [this message]
2004-06-16 22:29           ` Antonino A. Daplas
2004-06-16 22:39             ` Andrew Morton
2004-06-17 18:24             ` [PATCH][RIVAFB] rivafb: fb accel capabilities David Eger
2004-06-16 17:34       ` [PATCH][RIVAFB]: Updates to rivafb driver David Eger
2004-06-16 22:29         ` Antonino A. Daplas
2004-06-17  0:16           ` David Eger
2004-06-17 16:34             ` Benjamin Herrenschmidt

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=20040616132318.1435b0c7.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=adaplas@pol.net \
    --cc=eger@havoc.gtf.org \
    --cc=jsimmons@pentafluge.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).