From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] kmemcheck for mainline
Date: Fri, 12 Jun 2009 18:45:03 +0200 [thread overview]
Message-ID: <20090612164503.GA23608@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.01.0906120933120.3237@localhost.localdomain>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Fri, 12 Jun 2009, Vegard Nossum wrote:
> >
> > Please consider pulling the kmemcheck tree;
>
> No.
>
> This seems to be 99% merges o fother branches.
>
> I'm no longer pulling from people who can't keep their branches
> clean and develop without pulling from me every other day, or
> pulling from other random branches. If it gets that many
> conflicts, I just don't want to see it - there's something
> seriously wrong with it.
>
> And if you just merge for some random reason, I don't want to pull
> it either.
>
> So in either case, I'm not pulling this.
>
> Just _look_ at that gitk thing. It has several stretches of just
> "Merge branch 'linus' into kmemcheck". WITH NO OTHER DEVELOPMENT
> IN BETWEEN!
This is an ancient one year old tree :-/
Vegard, i suspect you are best off by creating a clean, rebased
(same-content) series linear tree out of the patches - with all
fixes backmerged and there being a good logical order of patches.
Since it will be same-content it should be doable in short order. I
can do it too if you dont have the time.
Ingo
next prev parent reply other threads:[~2009-06-12 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 13:31 [GIT PULL] kmemcheck for mainline Vegard Nossum
2009-06-12 13:57 ` Pekka Enberg
2009-06-12 14:00 ` Ingo Molnar
2009-06-12 16:38 ` Linus Torvalds
2009-06-12 16:41 ` Linus Torvalds
2009-06-12 16:45 ` Ingo Molnar [this message]
2009-06-15 14:59 ` Vegard Nossum
2009-06-16 16:21 ` Pekka Enberg
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=20090612164503.GA23608@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@gmail.com \
/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