From: Jeff Garzik <jgarzik@pobox.com>
To: "Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>
Cc: Netdev <netdev@oss.sgi.com>, prism54-devel@prism54.org
Subject: Re: Re: [Prism54] CVS -> bk tree update
Date: Wed, 16 Jun 2004 16:30:55 -0400 [thread overview]
Message-ID: <40D0ADFF.1040208@pobox.com> (raw)
In-Reply-To: <20040616064303.GO6253@ruslug.rutgers.edu>
Luis R. Rodriguez wrote:
> Jeff,
>
> Ok 2.6.7 is out, we missed it. Now what, send a group of patches against that then?
Don't feel too bad, it was in release candidate status so any patches
submitted would not have gone into 2.6.7 anyway (unless they were
critical bug fixes).
I'll reply to your other email after a yummy bowl of Ramen noodles...
Jeff
next prev parent reply other threads:[~2004-06-16 20:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 19:16 [Prism54] CVS -> bk tree update Luis R. Rodriguez
2004-06-14 22:31 ` Jeff Garzik
2004-06-16 2:20 ` Luis R. Rodriguez
2004-06-16 3:10 ` Jeff Garzik
2004-06-16 5:11 ` Luis R. Rodriguez
2004-06-16 6:43 ` Luis R. Rodriguez
2004-06-16 20:22 ` Francois Romieu
2004-06-16 20:30 ` Jeff Garzik [this message]
2004-06-16 21:09 ` Jeff Garzik
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=40D0ADFF.1040208@pobox.com \
--to=jgarzik@pobox.com \
--cc=mcgrof@ruslug.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.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;
as well as URLs for NNTP newsgroup(s).