[opensuse-kernel] kernel update to 3.6.1?
Hi, Would it be possible to have an update from 3.6.0 to 3.6.1 for factory git repo? Because in 3.6.0, omapdrm module fails to build (and have been disbaled in config file) but it is fixed in 3.6.1. Once updated to 3.6.1, I will re-enable omapdrm to have a working DVI output. Guillaume -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Mon, Oct 08, 2012 at 06:41:56PM +0200, Guillaume Gardet wrote:
Hi,
Would it be possible to have an update from 3.6.0 to 3.6.1 for factory git repo? Because in 3.6.0, omapdrm module fails to build (and have been disbaled in config file) but it is fixed in 3.6.1. Once updated to 3.6.1, I will re-enable omapdrm to have a working DVI output.
Wow, 3.6.1 hasn't even been out for 24 hours, the majority of them being a weekend (Sunday). Jiri is notified of every single stable kernel update through email, so he knows about them when they happen. Please be patient. greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/08/2012 06:41 PM, Guillaume Gardet wrote:
Would it be possible to have an update from 3.6.0 to 3.6.1 for factory git repo?
Hi, no, kernel:head does not follow stable releases (see archives for the reason). It will be updated to 3.7-rc1 or rc2.
Once updated to 3.6.1, I will re-enable omapdrm to have a working DVI output.
Only kernel:stable will have 3.6.1. And I forgot to push yesterday, so it will sync this very late night. - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQcw25AAoJEL0lsQQGtHBJpnsP/2Amnc14XvIu1Y45d1akmE5H 68Rf3KLnsRNtiQR8NdFTlZgn3IqD8E+XJzIkWwRKIf+R22wc+HmocATl9weayAl/ eVx6G+PAx6XYiDxcuBXYa9Sj2hblBuEuuXO//juBLtyIddQBbBRAdV9oXkX61Bdg PfFnCv+I90qMV5AxM3xl6GVXSJHZTlS0zU+ie9hZ28J/pRqcfQJmkfE4fSbCo+bH bLUU64mwSybdNULFXQybKFtu/HGROyny+oiAZDuYjv0woLxQ6ohkdHHxBr/WVytw +CYzmrnRXSS2KdvXrBDs1F9cNcsoCAxBj3BKqI9ksjbX9SHvGh2yklDBhoPx11Oe TSNmRimt3DJK+4RPtsSpqiZBPneTAtQq17B84gBfYjXbQsZgLBYozUexHxzLFb4Q OcEjgqH6CYoLJ10/pgdZM+UfRZYjdlQ85au+Q1ivMkw0qS9aCDh361oh2EYsv+s9 +urEF0k65Ko0+7TVvJyNDYm5ZQ1tN5x6X538pQkfLaI0T1WSRSybOsQHEffDA+K7 undqkHzYK4pExFFkDXSkAotDBVzbctFKS86PEbJjvuh5yBW+CYZuqHdHtuUBihno AShVKKIDTmVF8/tG3QuNrGjlgSPm9mHL0PI+SkamBEKKyArauKHuSMTZWp34eHCk jGe3khsiCrAa3BMz7Ltu =QtVt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Monday, October 08, 2012 19:30:33 Jiri Slaby wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/08/2012 06:41 PM, Guillaume Gardet wrote:
Would it be possible to have an update from 3.6.0 to 3.6.1 for factory git repo?
Hi, no, kernel:head does not follow stable releases (see archives for the reason). It will be updated to 3.7-rc1 or rc2.
Once updated to 3.6.1, I will re-enable omapdrm to have a working DVI output.
Only kernel:stable will have 3.6.1. And I forgot to push yesterday, so it will sync this very late night.
What about getting 3.6.1 then into Factory? Please work with Coolo if this comes from stable since that's not the normal devel project, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 09.10.2012 09:41, Andreas Jaeger wrote:
On Monday, October 08, 2012 19:30:33 Jiri Slaby wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/08/2012 06:41 PM, Guillaume Gardet wrote:
Would it be possible to have an update from 3.6.0 to 3.6.1 for factory git repo?
Hi, no, kernel:head does not follow stable releases (see archives for the reason). It will be updated to 3.7-rc1 or rc2.
Once updated to 3.6.1, I will re-enable omapdrm to have a working DVI output.
Only kernel:stable will have 3.6.1. And I forgot to push yesterday, so it will sync this very late night.
What about getting 3.6.1 then into Factory?
Please work with Coolo if this comes from stable since that's not the normal devel project,
If it's ok for everyone, I just copypac from Kernel:stable - factory doesn't even have the 3.6.0 final ;( Greetings, Stephan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/09/2012 11:47 AM, Stephan Kulow wrote:
On 09.10.2012 09:41, Andreas Jaeger wrote:
On Monday, October 08, 2012 19:30:33 Jiri Slaby wrote:
On 10/08/2012 06:41 PM, Guillaume Gardet wrote:
Once updated to 3.6.1, I will re-enable omapdrm to have a working DVI output.
Only kernel:stable will have 3.6.1. And I forgot to push yesterday, so it will sync this very late night.
What about getting 3.6.1 then into Factory?
Please work with Coolo if this comes from stable since that's not the normal devel project,
If it's ok for everyone, I just copypac from Kernel:stable - factory doesn't even have the 3.6.0 final ;(
I'm not sure -- what does it mean to copypac from k:s? BTW. kernel:head has 3.6 final, there just was no SR? - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQdGXRAAoJEL0lsQQGtHBJkBAP/1Xm248QPOY06stEGwrh+Ti7 Ce27Tp9SCaUoUxIz51PdSJqdU+sDWNJ95eEpQw93Hctw7z5d21WyatqPEkTOeLMb i2MFrG6IjxgvI/9ggjsWZPxghYZgxo8cOR3MAXYIkLvhAGJqS+5IqPMcFNMbPWIM 9E0qTPS3xPOzVWaYywwuyWo7KLR1yvODIBbzFVHPyEXIuy9Fp4ckVHDcVdTwskB6 ti7qaap/fgOn39MWZ8m40z7UwGGyBU5wnSbsqArjIm4enuVHPRfw0jLMiHe3Ke2l xTVahU1QmKg5WeAs1Yywm/hCMmYiZNQnxrcuISjYto2KnZaTPy/fymJ/IXwDjpU2 FbPHeuBz8ijMgqSmdm9A4L+C6PHHBQ5yL33BZ6w5H8onySaOxVuFs3LQp+3DQTdT I7Jf/Q/8jwfn6/UdUNGiAYZWOANZA1fwQskqurbDn11ugBX4MpfITmUG7/Kg4HGE Qtkv01htM0dI+7zDZzRhuUcKGrW7dML5rdGVlEhO/dqcUyfech9R17I3GwiRyten xvk3TbLXhMxWm+3QQ0dMo9Vc7QOEifhWiCVn36/WX72KCcI8dt5Jhk9kNMb2J2ZN ralZtnwoKrf0u7oO3UzNTMOXCvoAaGwnSMGHD7+Ezz+aK4AGPpKxuP7pt0RgayZo jra6uGlg0K6Oz+FTUhVk =R88/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/9/12 1:58 PM, Jiri Slaby wrote:
On 10/09/2012 11:47 AM, Stephan Kulow wrote:
On 09.10.2012 09:41, Andreas Jaeger wrote:
On Monday, October 08, 2012 19:30:33 Jiri Slaby wrote:
On 10/08/2012 06:41 PM, Guillaume Gardet wrote:
Once updated to 3.6.1, I will re-enable omapdrm to have a working DVI output.
Only kernel:stable will have 3.6.1. And I forgot to push yesterday, so it will sync this very late night.
What about getting 3.6.1 then into Factory?
Please work with Coolo if this comes from stable since that's not the normal devel project,
If it's ok for everyone, I just copypac from Kernel:stable - factory doesn't even have the 3.6.0 final ;(
I'm not sure -- what does it mean to copypac from k:s?
BTW. kernel:head has 3.6 final, there just was no SR?
I could've sworn I issued it as soon as I saw builds complete. If not, it's only accidental. Then there's the issue of whether we want -stable releases in Factory at all. It seems like a strange proposition to have -stable updates *AND* -rc kernels in the same project when it's not in the final stages of an official release cycle. OTOH, Tumbleweed shouldn't be ahead of Factory and it often is. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQdGfeAAoJEB57S2MheeWyaYsP/Ai0y/+klV9zWN6YtL3nlync OHT3w6gqbiurI+WobuwqdIslwSkopWDNB/cnpho0wm7JKN9ODFQCPOF9hj2r4H3s FTY18xCQLEqvOi71advXFNjH/3/Dnsi+JsT6zi7fB749/4+rMDxDS4NSjEhC4e7V C06DWytks4riA4CfVRxf3OuFiPFizU11xs5Eo1W+sIwQbqlB7abodEx11w0uwKsY REkLBfFSubv9t346Uxk/VW1nWEn6WFR3zDb0gvXt9pc4WKTSGQKJchl3njil9GRh LrMPPKPULX9p95LeTfFhRdox3jHpLQlNCuk+E/Ol19rOlPJ2C9StZFAyh1Ha3l35 SpjEmJGV7qXJjNwtRHm0SsF8AW756xeS9zeVNoNnQAUnZGG2l25VWceVPrRv7RG2 4Nz8zBdN+5G0/B6dFbB7TEx7W1k+KQePL+HgSCdai0+189/4xbR68DFeRK1ViYcV 6xfer5Zyg4dIBnGgfH4WzmTtG9OKljm/PaXXYN8+fch8k4dCZ9i+mwZWMlW3RvS1 m0kRtUCHl80VNrXIf9UQK0JBJZETxHm2FcJEMFJ/7JpqNWuYiu9/0u1FtYVyJxa7 z3LtoIozrCFZKj+DNOyvlkC6cWBPBASAtiym2XamoWkEEHuMAOodijnIj7ulU8cR Ri7IjglBwCc4+HtnAunH =A6yZ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Hi,
I don't see any value to keep factory buggy on purpose while 3.7 is shaping up.
Kernel:head can stay what it is and I just take a kernel from the stable series just as Greg is doing for tumbleweed.
And once you're ready for 3.7 we switch to it again. The only problem is the changes files being from different branches, but for the factory users it would only go forward in kernel versions.
Stephan (in the train)
Jeff Mahoney
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/9/12 1:58 PM, Jiri Slaby wrote:
On 10/09/2012 11:47 AM, Stephan Kulow wrote:
On 09.10.2012 09:41, Andreas Jaeger wrote:
On Monday, October 08, 2012 19:30:33 Jiri Slaby wrote:
On 10/08/2012 06:41 PM, Guillaume Gardet wrote:
Once updated to 3.6.1, I will re-enable omapdrm to have a working DVI output.
Only kernel:stable will have 3.6.1. And I forgot to push yesterday, so it will sync this very late night.
What about getting 3.6.1 then into Factory?
Please work with Coolo if this comes from stable since that's not the normal devel project,
If it's ok for everyone, I just copypac from Kernel:stable - factory doesn't even have the 3.6.0 final ;(
I'm not sure -- what does it mean to copypac from k:s?
BTW. kernel:head has 3.6 final, there just was no SR?
I could've sworn I issued it as soon as I saw builds complete. If not, it's only accidental.
Then there's the issue of whether we want -stable releases in Factory at all. It seems like a strange proposition to have -stable updates *AND* -rc kernels in the same project when it's not in the final stages of an official release cycle. OTOH, Tumbleweed shouldn't be ahead of Factory and it often is.
- -Jeff
- -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQIcBAEBAgAGBQJQdGfeAAoJEB57S2MheeWyaYsP/Ai0y/+klV9zWN6YtL3nlync OHT3w6gqbiurI+WobuwqdIslwSkopWDNB/cnpho0wm7JKN9ODFQCPOF9hj2r4H3s FTY18xCQLEqvOi71advXFNjH/3/Dnsi+JsT6zi7fB749/4+rMDxDS4NSjEhC4e7V C06DWytks4riA4CfVRxf3OuFiPFizU11xs5Eo1W+sIwQbqlB7abodEx11w0uwKsY REkLBfFSubv9t346Uxk/VW1nWEn6WFR3zDb0gvXt9pc4WKTSGQKJchl3njil9GRh LrMPPKPULX9p95LeTfFhRdox3jHpLQlNCuk+E/Ol19rOlPJ2C9StZFAyh1Ha3l35 SpjEmJGV7qXJjNwtRHm0SsF8AW756xeS9zeVNoNnQAUnZGG2l25VWceVPrRv7RG2 4Nz8zBdN+5G0/B6dFbB7TEx7W1k+KQePL+HgSCdai0+189/4xbR68DFeRK1ViYcV 6xfer5Zyg4dIBnGgfH4WzmTtG9OKljm/PaXXYN8+fch8k4dCZ9i+mwZWMlW3RvS1 m0kRtUCHl80VNrXIf9UQK0JBJZETxHm2FcJEMFJ/7JpqNWuYiu9/0u1FtYVyJxa7 z3LtoIozrCFZKj+DNOyvlkC6cWBPBASAtiym2XamoWkEEHuMAOodijnIj7ulU8cR Ri7IjglBwCc4+HtnAunH =A6yZ -----END PGP SIGNATURE-----
-- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/9/12 3:41 PM, Stephan Kulow wrote:
Hi,
I don't see any value to keep factory buggy on purpose while 3.7 is shaping up.
When it's not leading up to a release, no. When it is, we want the late -rc time to have users do testing on the actual kernel that we'll use for release. If we wait until .0, then we lose weeks of testing at a critical time in the cycle.
Kernel:head can stay what it is and I just take a kernel from the stable series just as Greg is doing for tumbleweed.
And once you're ready for 3.7 we switch to it again. The only problem is the changes files being from different branches, but for the factory users it would only go forward in kernel versions.
That's fine but 3.8 will probably be around release-time for 12.3 and we'll want to start doing -rc's again. I usually start with -rc2 because -rc1 can be pretty unstable. - -JEff
Jeff Mahoney
schrieb: On 10/9/12 1:58 PM, Jiri Slaby wrote:
On 10/09/2012 11:47 AM, Stephan Kulow wrote:
On 09.10.2012 09:41, Andreas Jaeger wrote:
On Monday, October 08, 2012 19:30:33 Jiri Slaby wrote:
On 10/08/2012 06:41 PM, Guillaume Gardet wrote:
Once updated to 3.6.1, I will re-enable omapdrm to have a working DVI output.
Only kernel:stable will have 3.6.1. And I forgot to push yesterday, so it will sync this very late night.
What about getting 3.6.1 then into Factory?
Please work with Coolo if this comes from stable since that's not the normal devel project,
If it's ok for everyone, I just copypac from Kernel:stable - factory doesn't even have the 3.6.0 final ;(
I'm not sure -- what does it mean to copypac from k:s?
BTW. kernel:head has 3.6 final, there just was no SR?
I could've sworn I issued it as soon as I saw builds complete. If not, it's only accidental.
Then there's the issue of whether we want -stable releases in Factory at all. It seems like a strange proposition to have -stable updates *AND* -rc kernels in the same project when it's not in the final stages of an official release cycle. OTOH, Tumbleweed shouldn't be ahead of Factory and it often is.
-Jeff
-- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
- -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQdILpAAoJEB57S2MheeWyfzQP/02t9NlJ84RHdh6ptqpT1KG9 5t/LjFdDPUAf8Xem71MI42md7AyoRpZ/xDt1a+pbTAbvJdCFYJvYVBbk4DmYxkgm neQkzuMdCgyuy5Nf8TSD+AS26M+0xZtH+T6nK1h6BX5ykqnataSDW1/dSYNkAFBc Jt46OTqJhKv7p729gdDJeTSOBfBs7kz5TxfUGo/M9QxjdzMt99FlY17mBnpSpkBX ZptSHBjY1HpK0S5cTif8wgEwfj3ubLP7p7iSbk3ovstdZaWM7+l5SllurFSTqJXq XubPfqPhGUq+/pnb1T+8MZtKvq/TbmW3FVWvMiIxwAGvI8HuahnLT1ywxrd2+sFx rKklo1dl7RC06YJPbmwk3WjaSoaYLJn9x/+EAkNHZPLrk90EYUk0Tzx6wFvMmjYP 6duKhUIv+Q/XD0ncRGpiVOxXE2zWQm9/YwjIKrtSNAi5THlIoN9yQyNAU3tJiGZk GBjwg0z0n8BLC9o70IayI+smfViFsf3wv6xbdEC0y2xs+A0WjB4GZmHSbaYzXECv n2gOeJdkeu5WNKE6DDee5dtlrQl1MyvQvCTCocF8QTsdgw59WhQGYvHYJhETd9ha nfcCVrarbUpeKny7nh2kvbcTjYIfE+rNw6om1+CdwfidAsYNZ+62Ue13dH8l0hQ8 /9Kp/vhKYey/7Xrhh0ak =pYjQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 09.10.2012 22:02, Jeff Mahoney wrote:
On 10/9/12 3:41 PM, Stephan Kulow wrote:
Hi,
I don't see any value to keep factory buggy on purpose while 3.7 is shaping up.
When it's not leading up to a release, no. When it is, we want the late -rc time to have users do testing on the actual kernel that we'll use for release. If we wait until .0, then we lose weeks of testing at a critical time in the cycle.
Kernel:head can stay what it is and I just take a kernel from the stable series just as Greg is doing for tumbleweed.
And once you're ready for 3.7 we switch to it again. The only problem is the changes files being from different branches, but for the factory users it would only go forward in kernel versions.
That's fine but 3.8 will probably be around release-time for 12.3 and we'll want to start doing -rc's again. I usually start with -rc2 because -rc1 can be pretty unstable.
That much is understood (even though it was me who pushed rc7 :), but between 3.7.0 and 3.8.0-rc2 are enough 3.7.X releases to talk about. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/10/2012 09:24 AM, Stephan Kulow wrote:
That's fine but 3.8 will probably be around release-time for 12.3 and we'll want to start doing -rc's again. I usually start with -rc2 because -rc1 can be pretty unstable.
That much is understood (even though it was me who pushed rc7 :), but between 3.7.0 and 3.8.0-rc2 are enough 3.7.X releases to talk about.
Ok, so what about pushing 3.7.X to kernel:head? For me there is no added work. I would just commit to the master branch instead of stable and merge master to stable as usual. - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQdSYtAAoJEL0lsQQGtHBJQKkP/Av0yMALKA3wfuxTRb4FG+Rk doCCMb4TNxTF9TUOvfaOs60ahg2EJZxy0PzEgchCTjhVDj3dn8oBm1Xka0Bs5s4L 05yWcls7U5MOPIV1eUYAlXKuE6oCGFxmEtORmXaXJTYOfxf7pC/5s9WXwhrjjE8J s+vJ5ysavJvcTmIWyp0UFqPBR358Mnuhcx00HqjtbxHWXJxr17NfrSqdx0YitnxL lt3Vh/xo4P91W+DsSvh8lfnPO/t1X1gdUq0RCJ9nPBp1mmMWwiKCR1qdWoUuwk+V ylLcXZBIxriw6KIRXAneDWMEQO02YG5u4PzJRY09wiedwQtbduR3I7VwXwvlUL2f D+BQLm8pd2afGf3sFxtB9lAAL5exjRIStL7nWlxrUyihqDppIOafUmMWR/2i0U7i AUswjSiz/4S8xk6Ndbq/9R5yXm0iLQ6gRSCSQagbb+rmHA0au0/tgAzwQpFvsQEC xz/EfuDxqnNKK3MoAFaE1eGsmXZPCy4JYY0GPrq7t+AkBloQZ7bh6iqkN9rPy7JE wrWOBZ680F5Gdto3yZ71VDw/+W4yBwfNmccX58suisfUP3FunawDfiSPeB2ilQrK /zY16Spo0wOHboi+v5JYQTPg41JoO4HF7Q7e1go7/KQqntO89X2V5bKapXUNbCl7 7jpPu0xff+dNqIGSQESB =zGq1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/10/12 3:39 AM, Jiri Slaby wrote:
On 10/10/2012 09:24 AM, Stephan Kulow wrote:
That's fine but 3.8 will probably be around release-time for 12.3 and we'll want to start doing -rc's again. I usually start with -rc2 because -rc1 can be pretty unstable.
That much is understood (even though it was me who pushed rc7 :), but between 3.7.0 and 3.8.0-rc2 are enough 3.7.X releases to talk about.
Ok, so what about pushing 3.7.X to kernel:head? For me there is no added work. I would just commit to the master branch instead of stable and merge master to stable as usual.
If you want to pull in 3.x.y before I switch to RC's that's ok with me. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQdcNaAAoJEB57S2MheeWyJ0YQAK7+FBVOj/64GryopYp2i5gD GFHUSTBB7oYG8eJtmgx5BAFolokzZOWZbFB4xrI42NBb+IejqbHDtkk0bWU8nTCV ZktAovQEIQnAAV7e4EEiCNr+FcK1+X3uM3Ode8hon46Ed749N4cf/Gr9F7h2i7Xs QKumflhLlRcQxB6dUXhjkxrkDoWqo9piYyog2Db+H+YWFETzqopro/aCKpP/IEWZ XsbhN1YIYYi3Axc78gOZKbr2Vt2ZuLrSDhNVL0uCBpvBgl6d9ltk+K6HwRPp2oX2 lIjVdawFNo+6PfldHcRzrh2jsYK4Jd4owliBvbWJeYEcRSYlnKiOIafLDVhfbMrW 5cedDbEshz6WSFmvOw9lt4v8tNxs16hDPcK49u3q3xAKy7eJS1xhGvXVXvRVvQK2 6VbL2+BfMx4U7D4/xfHnvdmXeTCF80qQFiX5VWu/Irg/FupNs5x7dplbqOUf3KhW p82ttsiIwFzWhyVmKxJj9JzPkvwytIA5Zrn9T+/YRm4lQ3QNQOAAfX1DT/v0U3Cu M8AaB3TKRMDVS3BR3Wf3IjTHIH/wRdGGCJndIv7py6DxnsA0uMPfQjSnEETjXiqh FJ83fankeLbfJnRfyfK1xfDElTvB1aZRLDrcsTQcis+m5WN3eoCU7jicdnmas/mT D628ImkjtivwHw/+2S3V =Tg3r -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/10/2012 08:50 PM, Jeff Mahoney wrote:
On 10/10/12 3:39 AM, Jiri Slaby wrote:
Ok, so what about pushing 3.7.X to kernel:head? For me there is no added work. I would just commit to the master branch instead of stable and merge master to stable as usual.
If you want to pull in 3.x.y before I switch to RC's that's ok with me.
Done. So from now on, Kernel:Head will look like: 3.6 3.6.1 3.6.2 or 3.7-rc2 whichever is released first. 3.7-rc3 ... 3.7-rcLAST 3.8 3.8.1 3.8.2 or 3.9-rc2 - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQdcrlAAoJEL0lsQQGtHBJMrMQAKMO5PzzdE3OCJf0sxtBml7N T0l7dIov0Fq1aGnk34w4NDuwPDO0zPvamZrg0i+7s2ZS7Zti0rlMb71BJdWXstsM PyYqlOAVe/L319toaGos+wIeABmMHni49lGGi85zf1KGWcPdHqXoLVec59fjLVJ0 uarg8Q81GiOo/vEpd9NVgGaqcsZzv3gEEK+5mh0gQJtyeTaJWR3w0aYixUlrYIf+ MXTuv+NbAMebVZKbwIhPfS+ZLrmJm+3Zx8WYZVv9HnvwXtTAV9f2AcLLB5rL5G0D uDhSb9oBQtimFcWRnjmLQssvv3TuHJBuX118P0OcCsTdDPnscalbGoOmxYUhegrE Pcoy4rXRNbYj99uRgZJdEZBRZmB83C09JECRMww34yLjjj//J0UUq7K9Vv1ot76C llK4l0jOMFcRc0UXJrQWUaq97sAphmyaM3lt/jtuKZX8EQNd9GYSDZd/vIV0etWM bHnA2QQ4v4Ftf3wgkBsZDk4+47wZpq5/XMbXMdfvqMGvQQGbXG6LkYFgoLs7YO+v idfvtUbq2uNFjs53RBRJsoeIyifOD8R7ke/mvcnxGP70ERK9+jXgzFngKUfPMeOD KJmmKV8Qz3bsx+IkI5B/2qrFt7W3b1yk9oKjCu8a0eBPJ955419vP04+5ae7tFzG M+1Wb7aF3mgPJL7CL9pe =8zSZ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/10/12 3:22 PM, Jiri Slaby wrote:
On 10/10/2012 08:50 PM, Jeff Mahoney wrote:
On 10/10/12 3:39 AM, Jiri Slaby wrote:
Ok, so what about pushing 3.7.X to kernel:head? For me there is no added work. I would just commit to the master branch instead of stable and merge master to stable as usual.
If you want to pull in 3.x.y before I switch to RC's that's ok with me.
Done. So from now on, Kernel:Head will look like: 3.6 3.6.1 3.6.2 or 3.7-rc2 whichever is released first. 3.7-rc3 ... 3.7-rcLAST 3.8 3.8.1 3.8.2 or 3.9-rc2
Yep and I expect that we'll probably create a new openSUSE-12.3 branch after 3.8. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQdctCAAoJEB57S2MheeWyZ6AP/3p+efUiXCvybaNZY+6WJUAo 5YcYIBD6yS+t+TeQCgvWr0fhRkhwnoQzxdtiGFnyH9bqO0oil1g8BFp/L5EIHOj7 vH0ocETpHLQ59iHfo04NSahM3fnM+xkScJpzCo06W8mBXZhM3Rk6h2l+LqdCZGNq VOkgBTtA8Otnd/Figafxd8AfJTVs3Uu/V7uOzO6y/ZSVHfwV8jGZVLyFsNgRxDuz SemQ2QZ5fCKpv+QKvDo1Yj0dgg84P8fGjKj+Ov900pR//R99FRHLYcAZuvCg7oMS nGp0f+qOa2qbEPWaH5d2M3t1u3hj0rdbni2RSb49waWJH+KGfjsHY7Ea1Qp8NjSU GUKtl3ES7hd/HUpBtI6CktByie1J8i7+QIv6U+H48QDABLHm96P5odxrv+u+tjVg jIK25bVjMIQXtF2y9ftNgMEm/qAS3iGYuctTURfZvDdF0i5ZR9XA0Y4roKg3+bh5 JySR9Amxe/Oig9XzzYYEFg31cr6TtUURh/RZ3xAvQZVHPPlvLuL07ViNEOoPnGbu TTP2PlOme/AOzlAdFSI+TcVSY0w0MQbMGVOh2vjJ+OsNQaOBEJx058OmMNpkV5zS nYF4Sg5DKtFtSzijcrRg+sJuccQwN/gwk2Z1bDCUlI8hhLKvy8cUwT146cjiyw+5 IgsSsOLaQ3Irslg4vAUy =aOv5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Wednesday 10 of October 2012 09:24EN, Stephan Kulow wrote:
That much is understood (even though it was me who pushed rc7 :), but between 3.7.0 and 3.8.0-rc2 are enough 3.7.X releases to talk about.
Most likely there will be only one. Sometimes it can happen that there are two, e.g. when 3.5.2 preceded 3.6-rc2, but even in that case it was only by one day. Michal Kubeček -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (8)
-
Andreas Jaeger
-
Greg KH
-
Guillaume Gardet
-
Jeff Mahoney
-
Jeff Mahoney
-
Jiri Slaby
-
Michal Kubeček
-
Stephan Kulow