From: grundler@dsl2.external.hp.com (Grant Grundler)
To: Sir Ace <chandler@nateng.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Um,
Date: Wed, 29 Jan 2003 18:53:45 -0700 [thread overview]
Message-ID: <20030130015345.GC12749@dsl2.external.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0301291311490.235-100000@jordan.eng.nateng.com>
On Wed, Jan 29, 2003 at 01:13:20PM -0800, Sir Ace wrote:
>
> I quickly browsed /patches, but there doesn't seem to be anything that
> tells about them, {mor ethan thier names} or if they have already been
> includeded in a tree....
the parisc-linux mail archive should say something about them.
> Is there a list of some sort or should I just use all the patches?
All patches not committed to CVS are experimental.
Don't take *any* of them unless you have evidence one of them
will solve a problem you are experiencing....and then if it
does, make noise so we know that particular patch needs to get
committed to CVS.
thanks,
grant
next prev parent reply other threads:[~2003-01-30 1:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 21:13 [parisc-linux] Um, Sir Ace
2003-01-30 1:53 ` Grant Grundler [this message]
2003-01-30 1:55 ` Sir Ace
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=20030130015345.GC12749@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=chandler@nateng.com \
--cc=parisc-linux@lists.parisc-linux.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