All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: dm-devel@redhat.com,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Alasdair G Kergon <agk@redhat.com>
Subject: please fetch new git-based DM 'for-next' branch [was: Re: [git pull] device-mapper changes for 3.11]
Date: Fri, 16 Aug 2013 17:18:10 -0400	[thread overview]
Message-ID: <20130816211810.GA8668@redhat.com> (raw)
In-Reply-To: <20130712110303.06095e7b41c49c35bcd61fab@canb.auug.org.au>

On Thu, Jul 11 2013 at  9:03pm -0400,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Alasdair,
> 
> On Thu, 11 Jul 2013 14:55:22 +0100 Alasdair G Kergon <agk@redhat.com> wrote:
> >
> > 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.
> 
> OK, noted.

Hi Stephen,

To access all future DM changes for linux-next, please switch from
Alasdair's quilt tree to using the 'for-next' branch of the DM git repo:

git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git

Thanks,
Mike

WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alasdair G Kergon <agk@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: please fetch new git-based DM 'for-next' branch [was: Re: [git pull] device-mapper changes for 3.11]
Date: Fri, 16 Aug 2013 17:18:10 -0400	[thread overview]
Message-ID: <20130816211810.GA8668@redhat.com> (raw)
In-Reply-To: <20130712110303.06095e7b41c49c35bcd61fab@canb.auug.org.au>

On Thu, Jul 11 2013 at  9:03pm -0400,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Alasdair,
> 
> On Thu, 11 Jul 2013 14:55:22 +0100 Alasdair G Kergon <agk@redhat.com> wrote:
> >
> > 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.
> 
> OK, noted.

Hi Stephen,

To access all future DM changes for linux-next, please switch from
Alasdair's quilt tree to using the 'for-next' branch of the DM git repo:

git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git

Thanks,
Mike

  reply	other threads:[~2013-08-16 21:18 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   ` [dm-devel] " Alasdair G Kergon
2013-07-12  1:03     ` Stephen Rothwell
2013-08-16 21:18       ` Mike Snitzer [this message]
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-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=20130816211810.GA8668@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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.