From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Thomas Molina <tmolina@home.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Who will be responsible for 2.4.0 patches?
Date: Sat, 04 Nov 2000 04:37:15 -0500 [thread overview]
Message-ID: <3A03D8CB.3DAC78CC@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011010754260.2018-100000@wr5z.localdomain>
Thomas Molina wrote:
> I want to make a minor change to the sound drivers Makefile for
> compiling pas16 as well as a modification to the documentation
> file. I'm told that since it is not a bugfix it needs to wait for post
> 2.4 final release.
Send me the patch... if its minor and useful, maybe it can go in.
Otherwise, yeah, you'll have to wait until 2.4.0 is released...
Jeff
--
Jeff Garzik | Dinner is ready when
Building 1024 | the smoke alarm goes off.
MandrakeSoft | -/usr/games/fortune
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-04 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 14:01 Who will be responsible for 2.4.0 patches? Thomas Molina
2000-11-04 9:37 ` Jeff Garzik [this message]
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=3A03D8CB.3DAC78CC@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@home.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