public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Lars Ellenberg <lars.ellenberg@linbit•com>
Cc: Andrew Morton <akpm@linux-foundation•org>,
	Philipp Reisner <philipp.reisner@linbit•com>,
	Bart Van Assche <bart.vanassche@gmail•com>,
	Kyle Moffett <kyle@moffetthome•net>,
	Christoph Hellwig <hch@infradead•org>, Neil Brown <neilb@suse•de>,
	Nikanth Karthikesan <knikanth@suse•de>, Greg KH <gregkh@suse•de>,
	James Bottomley <James.Bottomley@HansenPartnership•com>,
	Lars Marowsky-Bree <lmb@suse•de>,
	Jens Axboe <jens.axboe@oracle•com>, Dave Jones <davej@redhat•com>,
	Sam Ravnborg <sam@ravnborg•org>,
	drbd-dev@lists•linbit.com, linux-kernel@vger•kernel.org,
	linux-next@vger•kernel.org
Subject: Re: [Drbd-dev] [PATCH 00/16] drbd: a block device for HA clusters
Date: Wed, 22 Jul 2009 14:59:17 +1000	[thread overview]
Message-ID: <20090722145917.055eddc1.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090721185156.GA10126@johann>

[-- Attachment #1: Type: text/plain, Size: 989 bytes --]

Hi Lars,

On Tue, 21 Jul 2009 20:51:56 +0200 Lars Ellenberg <lars.ellenberg@linbit•com> wrote:
>
> Stephen: expect an explicit linux-next merge request
> within the next few days.

OK, just to be clear your tree should be based on Linus' tree (or some
other *stable*, non rebasing, tree - *not* linux-next).

[I guess your tree will fulfill all the following]

What I tell everyone: all patches/commits in the tree/series must
have been:

	posted to a relevant mailing list
	reviewed
	unit tested
	destined for the next merge window (or the current release)

*before* they are included.  The linux-next tree is for integration
testing and to lower the impact of conflicts between subsystems in the
next merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-07-22  4:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1246894775-10855-1-git-send-email-philipp.reisner@linbit.com>
2009-07-21  5:49 ` [PATCH 00/16] drbd: a block device for HA clusters Andrew Morton
     [not found]   ` <20090720224940.36da1ef8.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2009-07-21 18:51     ` Lars Ellenberg
2009-07-22  4:59       ` Stephen Rothwell [this message]
2009-07-24 15:20         ` [Drbd-dev] " Philipp Reisner
     [not found]           ` <200907241720.22771.philipp.reisner-63ez5xqkn6DQT0dZR+AlfA@public.gmane.org>
2009-07-26 23:24             ` 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=20090722145917.055eddc1.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=James.Bottomley@HansenPartnership$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=bart.vanassche@gmail$(echo .)com \
    --cc=davej@redhat$(echo .)com \
    --cc=drbd-dev@lists$(echo .)linbit.com \
    --cc=gregkh@suse$(echo .)de \
    --cc=hch@infradead$(echo .)org \
    --cc=jens.axboe@oracle$(echo .)com \
    --cc=knikanth@suse$(echo .)de \
    --cc=kyle@moffetthome$(echo .)net \
    --cc=lars.ellenberg@linbit$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=lmb@suse$(echo .)de \
    --cc=neilb@suse$(echo .)de \
    --cc=philipp.reisner@linbit$(echo .)com \
    --cc=sam@ravnborg$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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