From: Russell King <rmk@arm.linux.org.uk>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: More fbdev to pull
Date: Thu, 6 Jun 2002 15:56:21 +0100 [thread overview]
Message-ID: <adntgf$slt$2@main.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0206051410040.7204-100000@www.transvirtual.com>; from jsimmons@transvirtual.com on Thu, Jun 06, 2002 at 06:48:00AM -0700
On Thu, Jun 06, 2002 at 06:48:00AM -0700, James Simmons wrote:
> Now for the new rounds of updates. Please pull the fbdev BK updates and
> bug fixes.
>
> http://fbdev.bkbits.net:8080/fbdev-2.5
>
> Standard diff:
>
> http://www.transvirtual.com/~jsimmons/fbdev.diff.gz
diffstat output would be useful. Can you make it part of your standard
mailings please? That way, individual framebuffer maintainers know
whether they need to bother looking or not.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
next parent reply other threads:[~2002-06-06 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0206051410040.7204-100000@www.transvirtual.com>
2002-06-06 14:56 ` Russell King [this message]
[not found] <20020606155621.C21322@flint.arm.linux.org.uk>
2002-06-06 16:28 ` More fbdev to pull James Simmons
2002-06-06 13:48 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='adntgf$slt$2@main.gmane.org' \
--to=rmk@arm.linux.org.uk \
--cc=jsimmons@transvirtual.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 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).