From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: <linux-rdma@vger.kernel.org>
Subject: Re: git repo changes
Date: Thu, 27 Aug 2020 08:16:35 -0300 [thread overview]
Message-ID: <20200827111635.GF1152540@nvidia.com> (raw)
In-Reply-To: <2748fbb3-f443-f6e7-bb8e-92ac33bcc19b@gmail.com>
On Wed, Aug 26, 2020 at 09:51:40PM -0500, Bob Pearson wrote:
> The git master branch has vanished since a day or two ago. Should I
> be tracking for_next now or will master reappear?
for-next is the right thing
Jason
prev parent reply other threads:[~2020-08-27 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 2:51 git repo changes Bob Pearson
2020-08-27 11:16 ` Jason Gunthorpe [this message]
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=20200827111635.GF1152540@nvidia.com \
--to=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.com \
/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.