[New: openFATE 309637] Expanded kernel-source
Feature added by: Michal Marek (michal-m) Feature #309637, revision 1 Title: Expanded kernel-source Requested by: Michal Marek (michal-m) Developer: (Novell) Partner organization: openSUSE.org Description: Create a "mirror" of the kernel-source repository (http://gitorious.org/opensuse/kernel-source) that has the same commits as kernel-source, but the trees are actual linux sources with the suse patches applied. While this sounds easy and I have a working prototype already, there are a few gotchas to solve: * what to do with patches that do not apply (and with those that do apply, but only with a specific version of patch(1)) * what to do with really ancient suse trees that where the patch series was dependent on the architecture or flavor * how to do this incrementally and automatically after each kernel-source push Also a nice feature would be to merge with the upstream branch whenever the upstream version is updated, so that one has a single history to browse. Business case (Partner benefit): openSUSE.org: Easy browsing of the history, without having to decipher two columns with plus and minus signs. -- openSUSE Feature: https://features.opensuse.org/309637
Feature changed by: Jan Engelhardt (jengelh)
Feature #309637, revision 2
Title: Expanded kernel-source
Requested by: Michal Marek (michal-m)
Developer: (Novell)
Partner organization: openSUSE.org
Description:
Create a "mirror" of the kernel-source repository
(http://gitorious.org/opensuse/kernel-source) that has the same commits
as kernel-source, but the trees are actual linux sources with the suse
patches applied. While this sounds easy and I have a working prototype
already, there are a few gotchas to solve:
* what to do with patches that do not apply (and with those that do
apply, but only with a specific version of patch(1))
* what to do with really ancient suse trees that where the patch series
was dependent on the architecture or flavor
* how to do this incrementally and automatically after each kernel-
source push
Also a nice feature would be to merge with the upstream branch whenever
the upstream version is updated, so that one has a single history to
browse.
Business case (Partner benefit):
openSUSE.org: Easy browsing of the history, without having to decipher
two columns with plus and minus signs.
+ Discussion:
+ #1: Jan Engelhardt (jengelh) (2010-05-31 18:45:38)
+ To start with: an
Feature changed by: Michal Marek (michal-m)
Feature #309637, revision 3
Title: Expanded kernel-source
Requested by: Michal Marek (michal-m)
Developer: (Novell)
Partner organization: openSUSE.org
Description:
Create a "mirror" of the kernel-source repository
(http://gitorious.org/opensuse/kernel-source) that has the same commits
as kernel-source, but the trees are actual linux sources with the suse
patches applied. While this sounds easy and I have a working prototype
already, there are a few gotchas to solve:
* what to do with patches that do not apply (and with those that do
apply, but only with a specific version of patch(1))
* what to do with really ancient suse trees that where the patch series
was dependent on the architecture or flavor
* how to do this incrementally and automatically after each kernel-
source push
Also a nice feature would be to merge with the upstream branch whenever
the upstream version is updated, so that one has a single history to
browse.
Business case (Partner benefit):
openSUSE.org: Easy browsing of the history, without having to decipher
two columns with plus and minus signs.
Discussion:
#1: Jan Engelhardt (jengelh) (2010-05-31 18:45:38)
To start with: an
Feature changed by: Michal Marek (michal-m)
Feature #309637, revision 5
Title: Expanded kernel-source
Requested by: Michal Marek (michal-m)
Developer: (Novell)
Partner organization: openSUSE.org
Description:
Create a "mirror" of the kernel-source repository
(http://gitorious.org/opensuse/kernel-source) that has the same commits
as kernel-source, but the trees are actual linux sources with the suse
patches applied. While this sounds easy and I have a working prototype
already, there are a few gotchas to solve:
* what to do with patches that do not apply (and with those that do
apply, but only with a specific version of patch(1))
* what to do with really ancient suse trees that where the patch series
was dependent on the architecture or flavor
* how to do this incrementally and automatically after each kernel-
source push
Also a nice feature would be to merge with the upstream branch whenever
the upstream version is updated, so that one has a single history to
browse.
Business case (Partner benefit):
openSUSE.org: Easy browsing of the history, without having to decipher
two columns with plus and minus signs.
Discussion:
#1: Jan Engelhardt (jengelh) (2010-05-31 18:45:38)
To start with: an
Feature changed by: Michal Marek (michal-m)
Feature #309637, revision 6
Title: Expanded kernel-source
- Hackweek V: New
+ Hackweek V: Done
Priority
Requester: Important
Requested by: Michal Marek (michal-m)
Developer: (Novell)
Partner organization: openSUSE.org
Description:
Create a "mirror" of the kernel-source repository
(http://gitorious.org/opensuse/kernel-source) that has the same commits
as kernel-source, but the trees are actual linux sources with the suse
patches applied. While this sounds easy and I have a working prototype
already, there are a few gotchas to solve:
* what to do with patches that do not apply (and with those that do
apply, but only with a specific version of patch(1))
* what to do with really ancient suse trees that where the patch series
was dependent on the architecture or flavor
* how to do this incrementally and automatically after each kernel-
source push
Also a nice feature would be to merge with the upstream branch whenever
the upstream version is updated, so that one has a single history to
browse.
Business case (Partner benefit):
openSUSE.org: Easy browsing of the history, without having to decipher
two columns with plus and minus signs.
Discussion:
#1: Jan Engelhardt (jengelh) (2010-05-31 18:45:38)
To start with: an
participants (1)
-
fate_noreply@suse.de