From: Olof Johansson <olof@lixom.net>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, jk@ozlabs.org
Subject: Re: patchwork missing patches?
Date: Wed, 27 Feb 2008 16:34:25 -0600 [thread overview]
Message-ID: <20080227223425.GA24177@lixom.net> (raw)
In-Reply-To: <20080227093950.11c8f4af@zod.rchland.ibm.com>
On Wed, Feb 27, 2008 at 09:39:50AM -0600, Josh Boyer wrote:
> I'm trying to find some patches that went to the list recently in
> patchwork and they seem to be missing. Here are a few:
>
> http://ozlabs.org/pipermail/linuxppc-dev/2008-February/052196.html
I looked up the first one:
http://patchwork.ozlabs.org/linuxppc/patch&id=17004
> There might be more. Maybe I'm just blind, but I can't find them at
> all in patchwork.
The above is marked "Awaiting Upstream", maybe that's filtering it out
from your default list?
-Olof
next prev parent reply other threads:[~2008-02-27 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 15:39 patchwork missing patches? Josh Boyer
2008-02-27 22:34 ` Olof Johansson [this message]
2008-02-27 23:00 ` Paul Mackerras
2008-02-28 1:35 ` Josh Boyer
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=20080227223425.GA24177@lixom.net \
--to=olof@lixom.net \
--cc=jk@ozlabs.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.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).