public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-next@vger.kernel.org, Len Brown <lenb@kernel.org>,
	Dave Jones <davej@redhat.com>, Jean Delvare <khali@linux-fr.org>,
	Greg KH <greg@kroah.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	Sage Weil <sage@newdream.net>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Christoph Lameter <cl@linux-foundation.org>,
	Tejun Heo <tj@kernel.org>, Rusty Russell <rusty@rustcorp.com.au>,
	Al Viro <viro@ZenIV.linux.org.uk>, J??rn Engel <joern@logfs.org>
Subject: Re: linux-next: current pending merge fix patches
Date: Mon, 1 Mar 2010 10:19:16 +0100	[thread overview]
Message-ID: <20100301091916.GA30098@elte.hu> (raw)
In-Reply-To: <20100301085613.GA2867@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> > So i'd argue to not backmerge during the merge window (and i have stopped 
> > doing that myself a few cycles ago, and it clearly helped things) - but in 
> > any case it's certainly no big deal and up to Linus i guess.
> 
> What i do instead is that once Linus pulls from me i pull back immediately 
> to test, and if it's fine i base further subsystem patches on that and test 
> the heck out of the combination from that point on.

A sidenote: this is only advisable if the testing in the subsystem tree is 
strong, if there were many changes with interactions and if Linus's tree is 
still in its stable phase (like now).

For slower-pace subsystems it's often good to be even more conservative with 
backmerges: to wait until -rc1 with any backmerges and to to generally not 
backmerge non-rc-release versions of Linus's tree.

That way the development commits and the followup fix commits stay in one 
linear branch of history, with no backmerge inbetween, easily bisectable and 
testable on a stable base all the way.

Thanks,

	Ingo

  reply	other threads:[~2010-03-01  9:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01  5:04 linux-next: current pending merge fix patches Stephen Rothwell
2010-03-01  8:10 ` Ingo Molnar
2010-03-01  8:55   ` Stephen Rothwell
2010-03-01  9:01     ` Ingo Molnar
2010-03-01  8:56   ` Ingo Molnar
2010-03-01  9:19     ` Ingo Molnar [this message]
2010-03-01 15:17 ` 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=20100301091916.GA30098@elte.hu \
    --to=mingo@elte.hu \
    --cc=bfields@fieldses.org \
    --cc=cl@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=greg@kroah.com \
    --cc=joern@logfs.org \
    --cc=khali@linux-fr.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=rusty@rustcorp.com.au \
    --cc=sage@newdream.net \
    --cc=sfr@canb.auug.org.au \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=trond.myklebust@fys.uio.no \
    --cc=viro@ZenIV.linux.org.uk \
    /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