All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Tejun Heo <tj@kernel.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: manual merge of the lost-spurious-irq tree with the tip tree
Date: Tue, 5 Oct 2010 09:01:23 +0200	[thread overview]
Message-ID: <20101005070123.GF12267@elte.hu> (raw)
In-Reply-To: <20101005174524.b62d14a1.sfr@canb.auug.org.au>


* Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Not sure what I can do beyond making sure that all relevant people are 
> informed about what trees are being merged. [...]

Fortunately there's a really simple solution: wait for an explicit reply 
from a maintainer before adding a new-feature tree. (Solicite again via 
a To: email if the Cc: went unanswered by the maintainers.)

Could you please start using that method for all subsystems i 
co-maintain?

Thanks,

	Ingo

  reply	other threads:[~2010-10-05  7:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05  3:13 linux-next: manual merge of the lost-spurious-irq tree with the tip tree Stephen Rothwell
2010-10-05  3:20 ` Stephen Rothwell
2010-10-05  5:47 ` Tejun Heo
2010-10-05  6:32   ` Ingo Molnar
2010-10-05  6:45     ` Stephen Rothwell
2010-10-05  7:01       ` Ingo Molnar [this message]
2010-10-05  8:38         ` Stephen Rothwell
2010-10-05  9:12           ` Ingo Molnar
2010-10-05  6:55     ` Tejun Heo
2010-10-05  6:59       ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2010-10-05  3:12 Stephen Rothwell

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=20101005070123.GF12267@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    --cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.