From: Ingo Molnar <mingo@elte.hu>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [GIT PULL/NEXT] sched/arch: Introduce the finish_arch_post_lock_switch() scheduler callback
Date: Tue, 13 Mar 2012 13:20:53 +0100 [thread overview]
Message-ID: <20120313122053.GA17549@elte.hu> (raw)
In-Reply-To: <20120313120014.GB13220@flint.arm.linux.org.uk>
* Russell King <rmk@arm.linux.org.uk> wrote:
> Why am _I_ responsible for which kernel version _Catalin_ used
> for _his_ patches when _he_ committed them?
If you then pull that tree from him and push it out to
linux-next? Then *of course* you are responsible, it was your
decision to pull it.
I frequently reject pulls from subsystem maintainers on similar
(and sometimes lesser) grounds - because such mistakes tend to
compound with time.
The thing is, if you do Git pulls from someone then you must be
absolutely anal about it, because you cannot really fix things
up after the fact. The people you pull from must be your
extended arms, they must be doing an equal or better job than
you. That gives a basis of trust.
Once that is established, you can be permissive about mistakes.
But arguing that you are not responsible for what you pull is
absolutely grotesque and establishes a new low for this
discussion really...
Also, as I told you in the very first mail, I am *fine* with
this having happened, so you having zapped the commits is
indefensible IMO. Mistakes do happen and the patch is fine
technically and sfr and Linus could have handled the trivial
conflict. What I suggested was to do it a bit better in the
future. Is that too much to ask for?
> You're insane. Totally.
I think you owe me an apology :-(
Thanks,
Ingo
next prev parent reply other threads:[~2012-03-13 12:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 0:08 linux-next: manual merge of the arm tree with Linus' tree Stephen Rothwell
2012-03-13 6:16 ` Ingo Molnar
2012-03-13 8:33 ` Russell King
2012-03-13 8:36 ` Ingo Molnar
2012-03-13 8:47 ` Russell King
2012-03-13 8:56 ` Ingo Molnar
2012-03-13 9:00 ` Russell King
2012-03-13 9:26 ` [GIT PULL/NEXT] sched/arch: Introduce the finish_arch_post_lock_switch() scheduler callback Ingo Molnar
2012-03-13 9:50 ` Russell King
2012-03-13 10:19 ` Ingo Molnar
2012-03-13 11:27 ` Russell King
2012-03-13 11:56 ` Ingo Molnar
2012-03-13 12:00 ` Russell King
2012-03-13 12:20 ` Ingo Molnar [this message]
2012-03-13 12:36 ` Russell King
2012-03-13 13:02 ` Ingo Molnar
2012-03-13 12:10 ` Ingo Molnar
2012-03-13 12:17 ` Russell King
2012-03-13 12:44 ` Ingo Molnar
2012-03-13 13:04 ` Russell King
2012-03-13 13:31 ` Ingo Molnar
2012-03-13 15:47 ` Ingo Molnar
2012-03-30 13:52 ` Catalin Marinas
2012-03-30 14:25 ` Ingo Molnar
2012-03-30 17:21 ` Catalin Marinas
2012-03-13 11:11 ` Catalin Marinas
2012-03-13 8:48 ` linux-next: manual merge of the arm tree with Linus' tree Ingo Molnar
2012-03-13 8:58 ` Russell King
2012-03-13 9:06 ` Ingo Molnar
2012-03-13 9:09 ` Russell King
2012-03-13 9:11 ` Russell King
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=20120313122053.GA17549@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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).