All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alasdair G Kergon <agk@redhat.com>,
	Yann Droneaud <ydroneaud@opteya.com>,
	Mike Snitzer <snitzer@redhat.com>, Robin Dong <sanbai@taobao.com>,
	linux-kernel@vger.kernel.org, Jim Ramsay <jim_ramsay@dell.com>,
	dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
	Jun'ichi Nomura <j-nomura@ce.jp.nec.com>,
	Rob Herring <robherring2@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Milan Broz <gmazyland@gmail.com>,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re: [dm-devel] [git pull] device-mapper changes for 3.11
Date: Thu, 11 Jul 2013 14:55:22 +0100	[thread overview]
Message-ID: <20130711135522.GN8530@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <20130711162040.8a82cb97a6c647c4f61f919b@canb.auug.org.au>

On Thu, Jul 11, 2013 at 04:20:40PM +1000, Stephen Rothwell wrote:
> Alistair, is there some reason that you cannot maintain some relatively
> stable git tree for me to fetch (instead of the quilt series).  

Well Mike Snitzer is becoming a joint maintainer and this also requires
changes to the workflow so watch this space.

> Also,
> there is not real reason to keep rebasing this stuff (especially just
> before sending it to Linus).
 
Most of the time the patches are decoupled from the rest of the tree
and the final linux-next kernel is the same regardless of where the
quilt tree is attached.  I maintain a single sequence of patches 
where the ones ready for upstream float up to the top and the
linux-next export is a by-product and not the primary output.

Anyway, like I say, we'll be changing things during the next couple of
cycles and we'll bear your suggestions in mind.

Alasdair

  parent reply	other threads:[~2013-07-11 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11  1:34 [git pull] device-mapper changes for 3.11 Alasdair G Kergon
2013-07-11  6:20 ` Stephen Rothwell
2013-07-11 13:35   ` Mike Snitzer
2013-07-12  1:01     ` Stephen Rothwell
2013-07-11 13:55   ` Alasdair G Kergon [this message]
2013-07-12  1:03     ` [dm-devel] " Stephen Rothwell
2013-08-16 21:18       ` please fetch new git-based DM 'for-next' branch [was: Re: [git pull] device-mapper changes for 3.11] Mike Snitzer
2013-08-16 21:18         ` Mike Snitzer
2013-08-19  0:13         ` 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=20130711135522.GN8530@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=gmazyland@gmail.com \
    --cc=j-nomura@ce.jp.nec.com \
    --cc=jim_ramsay@dell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mpatocka@redhat.com \
    --cc=robherring2@gmail.com \
    --cc=sanbai@taobao.com \
    --cc=sfr@canb.auug.org.au \
    --cc=snitzer@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=ydroneaud@opteya.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 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.