Re: Stable release candidate oddities

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Dec 08, 2018 at 02:59:10PM -0800, Guenter Roeck wrote:
> Hi folks,
> 
> I sometimes see stable release candidates move backwards in time.
> For example, in the last few days, for v4.4.y.queue:
> 
> Dec 08 06:55	v4.4.166
> Dec 06 23:36	v4.4.166-57-g4e21c8c946b3
> Dec 04 03:31	v4.4.166-21-g9caf29c799ac
> Dec 04 00:36	v4.4.166-17-g14d854102e8c
> Dec 03 04:35	v4.4.166-19-gb8c2abe84488
> Dec 02 01:07	v4.4.166
> 
> How comes?

Because the linux-stable-rc tree is generated based off of the quilt
tree and sometimes gets blown away and restarted when I do a release
series and push out the other (not 4.4.4) real updates.

And sometimes we delete patches, maybe that is why it went "down" in
number of patches by 2?

> Normally I would not notice (or comment). However, after
> v4.4.166 the default configuration for arc had changed,
> requiring different compilers for defconfig/allnoconfig.
> I had fixed this up, but now my builds are broken again
> due to the reverted changes.

Sorry, I'll push out the -rc testing versions now, so that doesn't
happen for your systems.

greg k-h



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux