linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Cort Dougan <cort@ppc.kernel.org>
To: Darron Froese <darron@calgary.westworld.ca>
Cc: linuxppc-dev@lists.linuxppc.org,
	linuxppc-ans-support@hellfire.dusers.drexel.edu
Subject: Re: ANS Patches en route to the 2.2.x kernel?
Date: Tue, 23 Mar 1999 20:57:15 -0700	[thread overview]
Message-ID: <19990323205715.A15285@persephone.ppc.kernel.org> (raw)
In-Reply-To: <199903230217.TAA11981@moses.odi.ca>; from Darron Froese on Mon, Mar 22, 1999 at 07:17:47PM -0700


Watch vger.  That's where all the patches go through for PPC.

I don't have an up-to-date copy of the ANS patches but should be getting
them soon.  ANS is on its way into the main kerenl but has taken quite a
while, yes.

} Is there a way to look and see if various patches have been
} sent/accepted/waiting in queue? I've grepped through some of the latest
} patches without finding it....anyone know where it is and it's status?

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  parent reply	other threads:[~1999-03-24  3:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-23  2:17 ANS Patches en route to the 2.2.x kernel? Darron Froese
1999-03-23 23:49 ` David T. McWherter
1999-03-24  3:57 ` Cort Dougan [this message]
1999-03-25  4:32   ` David T. McWherter
1999-04-01 20:08     ` Nicholas Olinsky
1999-04-02  0:07       ` Cort Dougan

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=19990323205715.A15285@persephone.ppc.kernel.org \
    --to=cort@ppc.kernel.org \
    --cc=darron@calgary.westworld.ca \
    --cc=linuxppc-ans-support@hellfire.dusers.drexel.edu \
    --cc=linuxppc-dev@lists.linuxppc.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).