[opensuse-kernel] openSUSE-12.2 branch
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - With openSUSE 12.2 Beta having been released, it's time to branch off to let it stabilize while the master branch moves forward to 3.5. I've created the openSUSE-12.2 branch and added the packages to OBS, but syncing isn't configured yet so they'll be stale for a short while (HEAD will still be up-to-date). Michal, when you get a chance can you set up the syncing to OBS? - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP0negAAoJEB57S2MheeWymH0P/AniobQJAmWK/qrufGK5Kuvx 2omSUwx/M/u4JGmDfCEmGou7xsMwxlOuC88H3ozn22wQhYtOS06WhpJeVRe4Po67 cX+BzG0QeRq0vvhF9H/LbBzDFOsypJmSIN8H07g/A8UelhZIk1idLY22QIfhWb3m 0EWOFBnBWl354Akf9+sNfKKUjESvJLJTIC8n8bQVDNsEcXZloKbsFWkz8KZki7YD OWV2hzfhgxG1irvyZ+J6tjPMZ2HoKt2WHbHwFTyfKAw0aBl0WNimR/5St7JwD48e 5OiupH8T65F4INmbhY/e5elagX5Al5BG1sxWR8TAFvWbiPcvRDRkA6Ufp/G7DTXc ITI5bDqdv9O4FoIhPZcRjP8tjQkxUCwlcgcPm+uPZsxvzK9xVFq0H7+J9ksLWe09 OLtwATeBm9sKWGnEHGy29e1yVjI+kN3df+NJTaSH+7jfGwDTqxbowWeQZu5G/5yY IMBvvNk0bIOmjRro05NnPB/Q6SG2u4Se/lODgGOXrjHJnlorGTNN7ekstaEuC1w3 Id5okCv9GZaN/su+S11FKQkZfPrTPvODeP6/WN5PfJhkzkVr2gPeb4ioiNpHhphc EiBfGbWBj4lhgThl2lU7Q0zr/Vhv8fSTG4dKTnkvaWyXaK3cqpMk54OFuurZyHX5 34olhaEf/5CBUoWuGysd =lVBg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 9.6.2012 00:07, Jeff Mahoney wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all -
With openSUSE 12.2 Beta having been released, it's time to branch off to let it stabilize while the master branch moves forward to 3.5.
I've created the openSUSE-12.2 branch and added the packages to OBS, but syncing isn't configured yet so they'll be stale for a short while (HEAD will still be up-to-date).
Michal, when you get a chance can you set up the syncing to OBS?
Done. Michal -- 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 06/11/2012 08:23 AM, Michal Marek wrote:
On 9.6.2012 00:07, Jeff Mahoney wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all -
With openSUSE 12.2 Beta having been released, it's time to branch off to let it stabilize while the master branch moves forward to 3.5.
I've created the openSUSE-12.2 branch and added the packages to OBS, but syncing isn't configured yet so they'll be stale for a short while (HEAD will still be up-to-date).
Michal, when you get a chance can you set up the syncing to OBS?
Done.
Michal
Thanks. BTW, I've pushed my 3.5-rc2 work as the merge-3.5 branch. Xen and ARM still need updating. A related proposal: I'm not actively involved in Tumbleweed but I know people are using it. We see bug reports against e.g. Linux 3.3 that only Tumbleweed uses. The current process is to just push master along every time there's a new upstream kernel revision. Would the people behind Tumbleweed benefit if, instead, I branch the last commit before I rev to 3.6 as "Tumbleweed-3.5" or something? - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP1jSeAAoJEB57S2MheeWyvTAQALOd1UJfXVOt5/GtxBe4EcXG m9jkVK5gf6OL4uNqc9lruJfra2CJMpULT+lu+A9st9mEijni+XCGDnAyxKEP+xXn 8CYY8WuGGQ5rKNDh8+Dr4f5ExHAyNF5ljpVCHsfcmbUrRnL441V0NfPmyJWLXr4J yM2HX86RI4FkQ85Gf87k/R9tosa7Jgmc/rBGGjIHvEWWcwnfmaV55Tuz97Lr4cp0 VrZ3zHeeSyUltKCqfoylRR87n9rZJ0kF18uHu/ohH4SGIdHn9BKVpuQsuk4NZT2g KTH2OLYo3Zp4RYguuOfpwWrA0mErQAz2gUqVXTgjB8pbOMRnfJnG8AU/MrW6a6/4 cCX3QlTpfXbhwSJxqqjIqRAfYOG7YmhZWTYVAi4CsED4rbAXs/m2T/wjOPDUiQ5Y SKtoT0K0l5LGXl4OaeTd5HePsKO8gvwRByBS22tGMHqMtXTrze8KYziiA/djUsKg szWGEJKvVU1ZckHVKHde5gGy3uXBpiIEk4oWN0YP220jj67W8gk+pyvilR4r0LYl htBPc2BEO5jsHv4iD+HKTCSy/WwtczYnGg5mTUkvI0om00TOb6stGbnp2iQi1uoq zv5ny9o0JaMp4xG6LHPtgqact1PPRSX9H7B1AVKwjSafy8oVedXY/N6YR0Oo9gfv 6cJ6KKeU0UzPaHsWxU/j =UPMX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Mon, Jun 11, 2012 at 02:10:39PM -0400, Jeff Mahoney wrote:
On 06/11/2012 08:23 AM, Michal Marek wrote:
On 9.6.2012 00:07, Jeff Mahoney wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all -
With openSUSE 12.2 Beta having been released, it's time to branch off to let it stabilize while the master branch moves forward to 3.5.
I've created the openSUSE-12.2 branch and added the packages to OBS, but syncing isn't configured yet so they'll be stale for a short while (HEAD will still be up-to-date).
Michal, when you get a chance can you set up the syncing to OBS?
Done.
Michal
Thanks.
BTW, I've pushed my 3.5-rc2 work as the merge-3.5 branch.
Xen and ARM still need updating.
A related proposal: I'm not actively involved in Tumbleweed but I know people are using it. We see bug reports against e.g. Linux 3.3 that only Tumbleweed uses. The current process is to just push master along every time there's a new upstream kernel revision. Would the people behind Tumbleweed benefit if, instead, I branch the last commit before I rev to 3.6 as "Tumbleweed-3.5" or something?
I'm following the kernel:stable/ tree for the kernel to put into Tumbleweed, so that's up to you and whom ever is maintaining that repo :) But I do think I should wait for 12.2 to come out before moving the Tumblweed kernel to 3.6, but given the proposed release dates, that shouldn't be a problem, right? thanks, 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 06/11/2012 02:22 PM, Greg KH wrote:
On Mon, Jun 11, 2012 at 02:10:39PM -0400, Jeff Mahoney wrote:
On 06/11/2012 08:23 AM, Michal Marek wrote:
On 9.6.2012 00:07, Jeff Mahoney wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all -
With openSUSE 12.2 Beta having been released, it's time to branch off to let it stabilize while the master branch moves forward to 3.5.
I've created the openSUSE-12.2 branch and added the packages to OBS, but syncing isn't configured yet so they'll be stale for a short while (HEAD will still be up-to-date).
Michal, when you get a chance can you set up the syncing to OBS?
Done.
Michal
Thanks.
BTW, I've pushed my 3.5-rc2 work as the merge-3.5 branch.
Xen and ARM still need updating.
A related proposal: I'm not actively involved in Tumbleweed but I know people are using it. We see bug reports against e.g. Linux 3.3 that only Tumbleweed uses. The current process is to just push master along every time there's a new upstream kernel revision. Would the people behind Tumbleweed benefit if, instead, I branch the last commit before I rev to 3.6 as "Tumbleweed-3.5" or something?
I'm following the kernel:stable/ tree for the kernel to put into Tumbleweed, so that's up to you and whom ever is maintaining that repo :)
Ok, I think that might be Jiri Slaby's playground.
But I do think I should wait for 12.2 to come out before moving the Tumblweed kernel to 3.6, but given the proposed release dates, that shouldn't be a problem, right?
No. I'm expecting 12.2 to come out before 3.6 is released anyway. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP1jkBAAoJEB57S2MheeWyDREP+gKgS1of1K09jo5ohsPx2RmF OLXYJxNNKqavEvr0rp9ug14KV/froJyL7KLlEc+go3QbVlX4i8A/pX2Pn4EIZCxP 0tvys7FO7lmixAlrcP5cYQXilLe3q/YXuh25zYytuRUybTQ3v6q9shVJtv4wY/3T /B7n3LkyPTrs5TQIJw7KOn4TsTvjIr4kXBmmlgvJXGBT6n4+rYzYrK2+E98uPy+G GNd+HDKWMZ3f3tjAJ+je8zXWptaYtBgA6UX6KB4TSK8MPcWBTrLffUUguDijV6TK nRVi0nH1ChUuIYMWUWOYF91UGVa+bIevUOGu8mIVqucmZU2wT6ff7muhuEsN3lbh 3Jsw1PoViXGiwQ/T3fYP8KS17tDvhPfwzVvjs5WHWliZ0mcG42r4fujC/fTdxMUq 1O22Q5k+2R4YgLgmQ3qW1R5q+3Qk/Q7zRYk8nitf91dc3rcxJ3ugExTVUriPRI7y Q58lNrU9uKc1xFlBpZbfKDBEAU97jXeKoKPFeop8/xZLlSKiD5jRjvMx6HyKsM7p UtAztaNiqVspwI6VKqOXV69FLvLuRCkWNKk1vu+vtZpHszW8wUxWmPq4zO80un+y xXvsXjbB/uYnXvxPRQrySlvhcp9z8KB2djnYZCESu4LK1g7LN1UmJ1Ql5AThP7if oTz5oeMw92BECtSGjLNL =z+vq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Mon, Jun 11, 2012 at 2:29 PM, Jeff Mahoney <jeffm@suse.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 06/11/2012 02:22 PM, Greg KH wrote:
On Mon, Jun 11, 2012 at 02:10:39PM -0400, Jeff Mahoney wrote:
On 06/11/2012 08:23 AM, Michal Marek wrote:
On 9.6.2012 00:07, Jeff Mahoney wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all -
With openSUSE 12.2 Beta having been released, it's time to branch off to let it stabilize while the master branch moves forward to 3.5.
I've created the openSUSE-12.2 branch and added the packages to OBS, but syncing isn't configured yet so they'll be stale for a short while (HEAD will still be up-to-date).
Michal, when you get a chance can you set up the syncing to OBS?
Done.
Michal
Thanks.
BTW, I've pushed my 3.5-rc2 work as the merge-3.5 branch.
Xen and ARM still need updating.
A related proposal: I'm not actively involved in Tumbleweed but I know people are using it. We see bug reports against e.g. Linux 3.3 that only Tumbleweed uses. The current process is to just push master along every time there's a new upstream kernel revision. Would the people behind Tumbleweed benefit if, instead, I branch the last commit before I rev to 3.6 as "Tumbleweed-3.5" or something?
I'm following the kernel:stable/ tree for the kernel to put into Tumbleweed, so that's up to you and whom ever is maintaining that repo :)
Ok, I think that might be Jiri Slaby's playground.
But I do think I should wait for 12.2 to come out before moving the Tumblweed kernel to 3.6, but given the proposed release dates, that shouldn't be a problem, right?
No. I'm expecting 12.2 to come out before 3.6 is released anyway.
- -Jeff
FYI: Coolo said in the last couple days he may need to push 12.2 back to Sept. (or later?) due to excessive current issues in factory. Thus 3.6 may just come first. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 12.06.2012 01:11, Greg Freemyer wrote:
FYI: Coolo said in the last couple days he may need to push 12.2 back to Sept. (or later?) due to excessive current issues in factory. Thus 3.6 may just come first.
This is exactly the kind of thinking that led to the current issues in factory. If 12.2 is pushed back, it will be frozen. 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 06/11/2012 08:10 PM, Jeff Mahoney wrote:
A related proposal: I'm not actively involved in Tumbleweed but I know people are using it. We see bug reports against e.g. Linux 3.3 that only Tumbleweed uses. The current process is to just push master along every time there's a new upstream kernel revision. Would the people behind Tumbleweed benefit if, instead, I branch the last commit before I rev to 3.6 as "Tumbleweed-3.5" or something?
Yeah, I would appreciate that. Otherwise I have to find that manually. But I would call it stable-3.5 or last-3.5... But it doesn't matter. thanks, - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP1jzcAAoJEL0lsQQGtHBJloYP/2y/xNi19ySzjR13t1diJYTh SxJQs1psuIBpQQNb85ofAF/93BRaWn2OHqFMx+SAL5owWMxGGazB+kGAX0bUChhr TMwm4m+gOE4+UQEoURdvQc7zER+cPOkznCgdjZjE6suo+UBT60Wo7jgLTTqJ8NUk 7tDKWyo3nZcO5axDGp2t9UMaxHWqhwlL5xOpoZTufbwmGWUJhkIPJBo1Tbkba3k7 voDpCKM6/EsYE20DP2OzgEzBPP4lab5mObUgr3bI6d1Scae4iKUyO2MtRWV6qZBA GmkTD+8VMeR32i+jRgxcn0k6PKW7LuoXE8YqD8E40ggbazNMKU0rQcWFCPh/htuL DzE91W8wkBuA0QHzFdfx5SLs26O71nLK6tOtEM3O5B0xs9YogaZbD23tuytCCI7Z 3z00cIVoXFCsPiAtf+MBZaMzZf0tEH/JEuM8ijsvqj+ZbDdmPXRCZvam5pgi6JGV hMiY/jryu2U/HQ+Y8ZQlFnwpUmgRoBSowUd+kF5xhc+Fvz+FqwYuLqCqEN6vr5uh bvU8VJhYARXiL74Hx69dDloLiMxAKZPLdZ8MVbeXEibzYtDu03kLosmS9aWFy0Ue vvwOQd958qfttfN/aB0yITN9tfLyyiwGofxynvZDOyHkkUXNDevYWWowhm7sJGQs F91AVNUFyVbOj8KaqLG9 =RYDP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 11.06.12 at 20:10, Jeff Mahoney <jeffm@suse.de> wrote: BTW, I've pushed my 3.5-rc2 work as the merge-3.5 branch.
With 12.2 branched off already, is there a reason for not putting this directly into master? Jan -- 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 06/12/2012 04:57 AM, Jan Beulich wrote:
On 11.06.12 at 20:10, Jeff Mahoney <jeffm@suse.de> wrote: BTW, I've pushed my 3.5-rc2 work as the merge-3.5 branch.
With 12.2 branched off already, is there a reason for not putting this directly into master?
I wanted to try getting everything updated in a separate branch before pulling into master this time. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP12FQAAoJEB57S2MheeWyovsP/2KGua3M+A2zVSKA5DdnXujD gI4pDWTaQErNqpTchH6IxpDmM4HrPYJajr0UGkiOr+4dlx7sI81mkh6aNQq43ZUx uWRZNGRf6MdflCqcUGaWzDdK0J590PDRnmrKqsBbQol0X8bZml8A8tipqLuARBPH HRH9LRXH0qgJ4SHie5ST+/l2A559wdBjSl89JZvn8VIxseISDLKcHa7rNIRGrLE8 AiQhqaJTsKOt2rtcsxpb/c8KKXVqPjMG+BoD/A/8P0I33zQssOqfKwiPd8Y8nVQz u8eN44YoTyC0Ex0vSAuErkYVxa1zOeObv5PpDqM30Iqz1UCH9vqHcfYFY9nF/ZhZ ZblZVlPboNCjUwR7iKbX0mZ3C5lPgJ1qSvLSNDp2FbACvsvSWbq9ygv5Q/R7CQsK 9xTq2PD4+r5SwL+i7ZeTohAExErPYy8ipWzKtsyyS3pR9Bn6o+apWIXZsA8pecS+ 2dn7lfWUTDxuqZA9GTEKJ0KLxd0ccUcKpPhryD3y2LVU1G00R/vz5VbGn7FzM5zZ 12ZRl7kyeQvGEogGQleZ3KcTYlKlspAgMc8NsjYUAuNobUACLwFCYb2JlqJx4ahj Y/TR+iv4RZXQS7RDL0ZXtk9lQ7h4657XAh4cJOEzFqqb2gt5dqmdVtqgSAFqu/m7 LO7dP5jpnaQc+YlwiOqh =4bSK -----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 06/12/2012 11:33 AM, Jeff Mahoney wrote:
On 06/12/2012 04:57 AM, Jan Beulich wrote:
On 11.06.12 at 20:10, Jeff Mahoney <jeffm@suse.de> wrote: BTW, I've pushed my 3.5-rc2 work as the merge-3.5 branch.
With 12.2 branched off already, is there a reason for not putting this directly into master?
I wanted to try getting everything updated in a separate branch before pulling into master this time.
Or that was the plan, at least. People keep adding stuff into master anyway, so all it's doing is creating more work. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP33dOAAoJEB57S2MheeWyBAcP/jRYeV/DXKwwYUB5Onz34Bv1 kGjNAaB27fWbYFri5+vN/a7Oj3hINbp9HCTGcZZEM226F0kSYgfSxyv1G7En4PwZ /RjCGQR9ppeeQSEPWa+YcG7i1PZlGJ4AK5IVclew+IS/ka51+9UK4jYuHcvcGlVY eRInZt1OZGe4LRCzYPoju8mEs4+CILuKnZVDlUR3Rq1dSQhMzPsHHmVJTz2Z1+yd CuB+BPrRBnbTDHrtiHrNmdC6jwtLvVBUNxedxbfNS8MAHEMSVbq2+fIqflW2ukX/ tgcRz3jeO+UEjUe8Kt58MxDOigkj49+XDGkMkfeyzXHL6CYuy9f9zm63JD4ko7un zB7qpbjY2BG2Uz5rA05T840uEZsAUkSYoerlNBA+52KTHJQncwiGfrxsqHCCP27r +EkhkNHEL7e9kB/L7v33CG+MRfaHmNc37e0xr3zyyYaPzkLeCwiAEWNhc8aA18UR /lcfnQBoex6oQV0koQz1hxYcla1eGWV1i/yAnZRwRTGOOw+BAdvvvbJ3RXA8Uita nel2JviZTdbG4oJo7NHDDPO4BYPbs4UfyObOUCkMbWFcMHbfAIqZdF/XkEVMnU0I Hz3vKTzHQ/h5FiNtzvGzWXWbQogkDFSf/SB8FXRyYSJRc/O+qo9RWPffZ0fv6PUv YLAWptXrSM42vvXwmAgY =bNuL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (7)
-
Greg Freemyer -
Greg KH -
Jan Beulich -
Jeff Mahoney -
Jiri Slaby -
Michal Marek -
Stephan Kulow