From: Paul Mackerras <paulus@samba.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, jk@ozlabs.org
Subject: Re: patchwork missing patches?
Date: Thu, 28 Feb 2008 10:00:00 +1100 [thread overview]
Message-ID: <18373.60272.351572.363687@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20080227093950.11c8f4af@zod.rchland.ibm.com>
Josh Boyer writes:
> 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
That one was in "awaiting upstream" state since I put it in the
bundle, then realized it should probably go through your tree, and
didn't apply it. I've put it back to "new" state now.
> http://ozlabs.org/pipermail/linuxppc-dev/2008-February/052164.html
I seem to recall putting that one in "changes requested" state, but
now I can't find it either. Strange...
> http://ozlabs.org/pipermail/linuxppc-dev/2008-February/052129.html
Not sure where that one has gone.
> http://ozlabs.org/pipermail/linuxppc-dev/2008-February/052050.html
I have been deleting patches that go through other maintainers to try
to keep the number of patches down to a manageable level, and that
includes ibm_newemac patches, since they go through Jeff Garzik.
That's probably what happened to this one. I'll leave ibm_newemac
patches alone if you promise to clean them up periodically. :)
Paul.
next prev parent reply other threads:[~2008-02-27 23:00 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
2008-02-27 23:00 ` Paul Mackerras [this message]
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=18373.60272.351572.363687@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--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).