From: sagi@grimberg.me (Sagi Grimberg)
Subject: Where are all the patches landing?
Date: Tue, 2 Aug 2016 17:49:22 +0300 [thread overview]
Message-ID: <7c785bb2-777a-10ff-dd42-c48c2e48cee6@grimberg.me> (raw)
In-Reply-To: <CAEqzOjvcKZWWvpsJQhc6AzmSLtauA0y7esK_cZdMi=0Ct0m1sg@mail.gmail.com>
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.
next prev parent reply other threads:[~2016-08-02 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 12:41 Where are all the patches landing? Robert Randall
2016-08-02 12:56 ` Robert Randall
2016-08-02 14:49 ` Sagi Grimberg [this message]
2016-08-02 15:53 ` Steve Wise
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=7c785bb2-777a-10ff-dd42-c48c2e48cee6@grimberg.me \
--to=sagi@grimberg.me \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).