From: Greg KH <greg@kroah.com>
To: Sven Joachim <svenjoac@gmx.de>
Cc: Rainer Fiebig <jrf@mailbox.org>, stable@vger.kernel.org
Subject: Re: 4.16-rc7 not (yet?) in stable.git
Date: Sat, 31 Mar 2018 18:20:03 +0200 [thread overview]
Message-ID: <20180331162003.GA25428@kroah.com> (raw)
In-Reply-To: <87fu4g6xh8.fsf@turtle.gmx.de>
On Sat, Mar 31, 2018 at 06:06:27PM +0200, Sven Joachim wrote:
> On 2018-03-31 17:48 +0200, Rainer Fiebig wrote:
>
> > 4.16-rc7 doesn't seem to be in stable.git yet.
>
> The tag is there, but the master branch still points at 4.16-rc6.
>
> > Am I too impatient or perhaps having a git-pull-problem here?
>
> It seems that Greg just needs to push the master branch.
Yeah, now pushed out, I don't always do it for all -rc releases. If you
want to track the -rc releases, use Linus's tree, not the stable tree.
You all do know about multiple repos for git trees, right? No need to
only depend on one of them for all of your needs...
thanks,
greg k-h
next prev parent reply other threads:[~2018-03-31 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 15:48 4.16-rc7 not (yet?) in stable.git Rainer Fiebig
2018-03-31 16:06 ` Sven Joachim
2018-03-31 16:20 ` Greg KH [this message]
2018-03-31 19:57 ` Rainer Fiebig
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=20180331162003.GA25428@kroah.com \
--to=greg@kroah.com \
--cc=jrf@mailbox.org \
--cc=stable@vger.kernel.org \
--cc=svenjoac@gmx.de \
/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