Where are all the patches landing?

Where are all the patches landing?

[Robert Randall]

Prepping for FMS demo.  Just want to make sure we're using the latest
code at the show.  I've seen much patching activity but I don't see
them landing in the nvme-fabrics repository.

Would one of the brilliant (honestly) contributors please educated me
on how to assemble the latest NVMeOF code?

Best regards,
Robert

-- 
Robert Randall | robert.r.randall at gmail.com

Where are all the patches landing?

[Robert Randall]

May have answered this already.  The patches appear to be landing on
the nvmf-4.9 branch.

Please let me know if I should be using a different branch.

THANKS!!
Robert

On Tue, Aug 2, 2016 at 7:41 AM, Robert Randall
<robert.r.randall@gmail.com> wrote:
> Prepping for FMS demo.  Just want to make sure we're using the latest
> code at the show.  I've seen much patching activity but I don't see
> them landing in the nvme-fabrics repository.
>
> Would one of the brilliant (honestly) contributors please educated me
> on how to assemble the latest NVMeOF code?
>
> Best regards,
> Robert
>
> --
> Robert Randall | robert.r.randall at gmail.com



-- 
Robert Randall | robert.r.randall at gmail.com

Where are all the patches landing?

[Sagi Grimberg]

Hi Robert,

> May have answered this already.  The patches appear to be landing on
> the nvmf-4.9 branch.
>
> Please let me know if I should be using a different branch.

We are maintaining two branches in nvme-fabrics.git

1. nvmf-<next-ver> for patches targeting the
next merge window (this is nvmf-4.9)

2. nvmf-<current-ver>-rc for patches targeting
the upcoming rc releases (usually bug fixes)

This is so Jens can have a clear look of what patches
exist and where they are targeted.

So, each patch will exist in either of the branches.

Where are all the patches landing?

[Steve Wise]

> 
> Hi Robert,
> 
> > May have answered this already.  The patches appear to be landing on
> > the nvmf-4.9 branch.
> >
> > Please let me know if I should be using a different branch.
> 
> We are maintaining two branches in nvme-fabrics.git
> 
> 1. nvmf-<next-ver> for patches targeting the
> next merge window (this is nvmf-4.9)
> 
> 2. nvmf-<current-ver>-rc for patches targeting
> the upcoming rc releases (usually bug fixes)
> 
> This is so Jens can have a clear look of what patches
> exist and where they are targeted.
> 
> So, each patch will exist in either of the branches.
> 

Thanks for explaining this.  I've been using Jens' for-linus branch for
linux-block repo...  I wasn't sure the nvmf repo was being maintained after the
merge...