All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
* ceph tree in linux-next
@ 2011-09-27 16:38 Sage Weil
  2011-09-27 23:01 ` Stephen Rothwell
  0 siblings, 1 reply; 6+ messages in thread
From: Sage Weil @ 2011-09-27 16:38 UTC (permalink / raw
  To: sfr; +Cc: ceph-devel

Hi Stephen,

Can you add the new Ceph tree location to linux-next?  

	git://github.com/NewDreamNetwork/ceph-client.git for-next

Thanks!
sage

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: ceph tree in linux-next
  2011-09-27 16:38 Sage Weil
@ 2011-09-27 23:01 ` Stephen Rothwell
  0 siblings, 0 replies; 6+ messages in thread
From: Stephen Rothwell @ 2011-09-27 23:01 UTC (permalink / raw
  To: Sage Weil; +Cc: ceph-devel

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

Hi Sage,

On Tue, 27 Sep 2011 09:38:24 -0700 (PDT) Sage Weil <sage@newdream.net> wrote:
>
> Can you add the new Ceph tree location to linux-next?  
> 
> 	git://github.com/NewDreamNetwork/ceph-client.git for-next

I will switch to that from today.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* ceph tree in linux-next
@ 2012-03-03  5:41 Sage Weil
  2012-03-03  7:22 ` Stephen Rothwell
  0 siblings, 1 reply; 6+ messages in thread
From: Sage Weil @ 2012-03-03  5:41 UTC (permalink / raw
  To: sfr; +Cc: ceph-devel

Hi Stephen,

The Ceph kernel tree has moved[1], and we've reworked the way we're 
managing commits in our tree.  Can you update linux-next to pull from

	git://github.com/ceph/ceph-client.git#master

That'll ensure that anything we've tested and reviewed gets into -next 
without us having to remember to push a for-next branch.

Thanks!
sage


[1] http://ceph.newdream.net/2012/03/the-git-repositories-have-moved/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: ceph tree in linux-next
  2012-03-03  5:41 ceph tree in linux-next Sage Weil
@ 2012-03-03  7:22 ` Stephen Rothwell
  2012-03-03 22:27   ` Sage Weil
  0 siblings, 1 reply; 6+ messages in thread
From: Stephen Rothwell @ 2012-03-03  7:22 UTC (permalink / raw
  To: Sage Weil; +Cc: ceph-devel

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

Hi Sage,

On Fri, 2 Mar 2012 21:41:00 -0800 (PST) Sage Weil <sage@newdream.net> wrote:
>
> The Ceph kernel tree has moved[1], and we've reworked the way we're 
> managing commits in our tree.  Can you update linux-next to pull from
> 
> 	git://github.com/ceph/ceph-client.git#master
> 
> That'll ensure that anything we've tested and reviewed gets into -next 
> without us having to remember to push a for-next branch.

Well, I can't really use your master branch because it has 3 commits on
the top of it that modify btrfs and are also not signed and do not look
like they are destined for Linus.

I need a clean branch that contains only what you will be sending to Linus.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: ceph tree in linux-next
  2012-03-03  7:22 ` Stephen Rothwell
@ 2012-03-03 22:27   ` Sage Weil
  2012-03-04 23:19     ` Stephen Rothwell
  0 siblings, 1 reply; 6+ messages in thread
From: Sage Weil @ 2012-03-03 22:27 UTC (permalink / raw
  To: Stephen Rothwell; +Cc: ceph-devel

On Sat, 3 Mar 2012, Stephen Rothwell wrote:
> Hi Sage,
> 
> On Fri, 2 Mar 2012 21:41:00 -0800 (PST) Sage Weil <sage@newdream.net> wrote:
> >
> > The Ceph kernel tree has moved[1], and we've reworked the way we're 
> > managing commits in our tree.  Can you update linux-next to pull from
> > 
> > 	git://github.com/ceph/ceph-client.git#master
> > 
> > That'll ensure that anything we've tested and reviewed gets into -next 
> > without us having to remember to push a for-next branch.
> 
> Well, I can't really use your master branch because it has 3 commits on
> the top of it that modify btrfs and are also not signed and do not look
> like they are destined for Linus.
> 
> I need a clean branch that contains only what you will be sending to Linus.

Yeah, it works better if I update the branch first.  We switched over to 
the testing branch for review and qa a while back but forgot to reset 
master.  It's clean now.

Thanks!
sage

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: ceph tree in linux-next
  2012-03-03 22:27   ` Sage Weil
@ 2012-03-04 23:19     ` Stephen Rothwell
  0 siblings, 0 replies; 6+ messages in thread
From: Stephen Rothwell @ 2012-03-04 23:19 UTC (permalink / raw
  To: Sage Weil; +Cc: ceph-devel

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

Hi Sage,

On Sat, 3 Mar 2012 14:27:18 -0800 (PST) Sage Weil <sage@newdream.net> wrote:
>
> Yeah, it works better if I update the branch first.  We switched over to 
> the testing branch for review and qa a while back but forgot to reset 
> master.  It's clean now.

Thanks.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2012-03-04 23:19 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-03  5:41 ceph tree in linux-next Sage Weil
2012-03-03  7:22 ` Stephen Rothwell
2012-03-03 22:27   ` Sage Weil
2012-03-04 23:19     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2011-09-27 16:38 Sage Weil
2011-09-27 23:01 ` Stephen Rothwell

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.