4.16-rc7 not (yet?) in stable.git

4.16-rc7 not (yet?) in stable.git

[Rainer Fiebig]

[-- Attachment #1.1: Type: text/plain, Size: 233 bytes --]


Hi!

4.16-rc7 doesn't seem to be in stable.git yet. Am I too impatient or perhaps having a git-pull-problem here?

Thanks!

Rainer Fiebig

-- 
The truth always turns out to be simpler than you thought.
Richard Feynman


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

Re: 4.16-rc7 not (yet?) in stable.git

[Sven Joachim]

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.

Cheers,
       Sven

Re: 4.16-rc7 not (yet?) in stable.git

[Greg KH]

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

Re: 4.16-rc7 not (yet?) in stable.git

[Rainer Fiebig]

Greg KH wrote:
> 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...

Yeah - but the idea of picking all the fruits from just one tree is just too alluring. ;)

Thanks to both of you!

Rainer Fiebig