From: Linus Torvalds <torvalds@linux-foundation.org>
To: Pekka Enberg <penberg@kernel.org>
Cc: cl@linux-foundation.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [GIT PULL] SLAB changes for v2.6.38
Date: Mon, 10 Jan 2011 08:44:03 -0800 [thread overview]
Message-ID: <AANLkTim0UBNG6bVgBDQsrBhVjS0FSdLbwaipBZGkTeWF@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101091110520.5270@tiger>
On Sun, Jan 9, 2011 at 1:13 AM, Pekka Enberg <penberg@kernel.org> wrote:
>
> It's been rather quiet for slab allocators this merge cycle. There's only
> few cleanups here. The bug fixes were merged in v2.6.37 already. As they
> were cherry-picked from this branch, they show up in the pull request
> (what's up with that btw).
For the "what's up with that btw" department:
A cherry-pick really is nothing but "apply the same patch as a
different commit".
So there is no way to say "this is already there" - because it really
isn't. It's a totally different thing. In fact, it would be very wrong
to filter them out, both from a fundamental design standpoint, but
also from a usability/reliability standpoint: cherry-picks are by no
means guaranteed to be identical to the source - like any "re-apply
the patch in another place" model, the end result is not at all
guaranteed to be semantically identical simply due to different bases:
the patches may not even be identical, and even if they are, the
results of the code may depend on what else is going on.
So don't think of cherry-picks as "the same commit". It's not, and it
never will be. It's a totally separate commit, they just share some
superficial commonalities.
Linus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-01-10 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 9:13 [GIT PULL] SLAB changes for v2.6.38 Pekka Enberg
2011-01-10 16:44 ` Linus Torvalds [this message]
2011-01-11 10:41 ` Pekka Enberg
2011-01-11 16:13 ` Linus Torvalds
2011-01-11 21:25 ` Tony Luck
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=AANLkTim0UBNG6bVgBDQsrBhVjS0FSdLbwaipBZGkTeWF@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@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;
as well as URLs for NNTP newsgroup(s).