linux-kernel - Re: [git pull] device-mapper changes for 3.11

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130711133511.GA12287@redhat.com>
Date:	Thu, 11 Jul 2013 09:35:11 -0400
From:	Mike Snitzer <snitzer@...hat.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Alasdair G Kergon <agk@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	dm-devel@...hat.com, linux-kernel@...r.kernel.org,
	Guenter Roeck <linux@...ck-us.net>,
	Hannes Reinecke <hare@...e.de>,
	Jim Ramsay <jim_ramsay@...l.com>,
	"Jun'ichi Nomura" <j-nomura@...jp.nec.com>,
	Mikulas Patocka <mpatocka@...hat.com>,
	Milan Broz <gmazyland@...il.com>,
	Rob Herring <robherring2@...il.com>,
	Robin Dong <sanbai@...bao.com>, stable@...r.kernel.org,
	Yann Droneaud <ydroneaud@...eya.com>, axboe@...nel.dk
Subject: Re: [git pull] device-mapper changes for 3.11

On Thu, Jul 11 2013 at  2:20am -0400,
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> On Thu, 11 Jul 2013 02:34:48 +0100 Alasdair G Kergon <agk@...hat.com> wrote:
> >
> > Please pull from:
> >  
> >   git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-dm tags/dm-3.11-changes
> > 
> > to get the following device-mapper changes for 3.11.
> 
> The device-mapper tree exists as a quilt series in linux-next.  The
> patches in the above git tree are the same as the ones in linux-next, but
> have a different base (and the ones in linux-next were on a different
> base from yesterday as well). :-(
> 
> Alistair, is there some reason that you cannot maintain some relatively
> stable git tree for me to fetch (instead of the quilt series).  Also,
> there is not real reason to keep rebasing this stuff (especially just
> before sending it to Linus).

Hi Stephen,

I'll be transitioning in to maintain device mapper (for 3.12).  Alasdair
will be helping me as needed but ultimately the plan is for me to be the
one sending DM changes upstream in the future.  I will maintain a
kernel.org git tree with a 'for-next' branch for you to pull.  I'll
likely base my for-next on Jens' for-next as a rule (unless that isn't
ideal on a linux-next process level).

There will be a learning curve for me initially on how to interface with
linux-next, proper git rebase protocol relative to Linus' ideals, etc
but I hope to cut through that quickly.

Regards,
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/