From: James Simmons <jsimmons@transvirtual.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: More fbdev to pull
Date: Thu, 6 Jun 2002 06:48:00 -0700 (PDT) [thread overview]
Message-ID: <adnpe6$j0v$2@main.gmane.org> (raw)
Hi!
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
. ---
|o_o |
|:_/ | Give Micro$oft the Bird!!!!
// \ \ Use Linux!!!!
(| | )
/'\_ _/`\
\___)=(___/
_______________________________________________________________
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 reply other threads:[~2002-06-06 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 13:48 James Simmons [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 13:48 More fbdev to pull James Simmons
2002-06-06 14:56 ` Russell King
2002-06-06 16:28 ` James Simmons
2002-06-06 16:28 ` James Simmons
2002-06-06 14:56 ` Russell King
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='adnpe6$j0v$2@main.gmane.org' \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.