From: Paul Jackson <pj@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Simon.Derr@bull.net
Subject: Re: How do I remove a patch buried in your *-mm series?
Date: Sun, 4 Dec 2005 01:08:23 -0800 [thread overview]
Message-ID: <20051204010823.fb512077.pj@sgi.com> (raw)
In-Reply-To: <20051204004437.327c9a8c.akpm@osdl.org>
Andrew wrote:
> So a patch against that will be ideal.
Ok - the "change-marker-for-relative-numbering" patch I wanted gone is
gone. Good.
I don't know what "patch against that" you have in mind. But I guess
that doesn't matter.
I will make sure I am in sync with that rc4 + that mm rollup patch +
whatever else follows it in mm, for whatever other work I do.
Thanks.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
prev parent reply other threads:[~2005-12-04 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 7:49 How do I remove a patch buried in your *-mm series? Paul Jackson
2005-12-04 8:15 ` Andrew Morton
2005-12-04 8:31 ` Paul Jackson
2005-12-04 8:44 ` Andrew Morton
2005-12-04 9:08 ` Paul Jackson [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=20051204010823.fb512077.pj@sgi.com \
--to=pj@sgi.com \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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