From: Jes Sorensen <jes@wildopensource.com>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: fbdev BK tree ready for testing.
Date: 23 Apr 2002 08:20:49 -0400 [thread overview]
Message-ID: <m3bscaobby.fsf@trained-monkey.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10204221516250.32538-100000@www.transvirtual.com>
>>>>> "James" == James Simmons <jsimmons@transvirtual.com> writes:
James> Hi!
James> I just finished sending up the last large change I like to
James> send to Linus for the framebuffer changes. Since I can't test
James> all the possible hardware there I like to ask people to test
James> the BK tree out. Once I have positive reports I like to merge
James> it with Linus BK tree. Thank you.
James> http://fbdev.bkbits.net/fbdev-2.5
ARGH
If you want people to test out the patches, posting a bitkeeper only
URL is totally unreasonable!
This is exactly what caused the long flame on linux-kernel the other
day ;-(
Jes
next prev parent reply other threads:[~2002-04-23 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 22:28 fbdev BK tree ready for testing James Simmons
2002-04-23 12:20 ` Jes Sorensen [this message]
2002-04-23 18: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=m3bscaobby.fsf@trained-monkey.org \
--to=jes@wildopensource.com \
--cc=jsimmons@transvirtual.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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