On 02/19/2017 12:32 PM, Mike Pagano wrote:
> Upstream does not version patches and every change breaks the manifest
> which
> breaks the tree. This results in a constant chasing of bugs since we can't
> predict the breakage.
>
> Signed-off-by: Mike Pagano
> ---
> eclass/kernel-2.eclass | 102
> +
On 02/19/2017 06:03 PM, Mike Gilbert wrote:
> On Sun, Feb 19, 2017 at 12:32 PM, Mike Pagano wrote:
>> Upstream does not version patches and every change breaks the manifest
>> which
>> breaks the tree. This results in a constant chasing of bugs since we can't
>> predict the breakage.
>
> Sounds
On 02/19/2017 05:55 PM, Andrew Savchenko wrote:
> On Sun, 19 Feb 2017 12:32:26 -0500 Mike Pagano wrote:
>> Upstream does not version patches and every change breaks the manifest
>> which
>> breaks the tree. This results in a constant chasing of bugs since we can't
>> predict the breakage.
>
> Ha
On Sun, Feb 19, 2017 at 12:32 PM, Mike Pagano wrote:
> Upstream does not version patches and every change breaks the manifest
> which
> breaks the tree. This results in a constant chasing of bugs since we can't
> predict the breakage.
Sounds good to me.
> @@ -1517,17 +1425,11 @@ kernel-2_src_pre
On Sun, 19 Feb 2017 12:32:26 -0500 Mike Pagano wrote:
> Upstream does not version patches and every change breaks the manifest
> which
> breaks the tree. This results in a constant chasing of bugs since we can't
> predict the breakage.
Have you tried to contact upstream and fix this issue there?
W dniu 19.02.2017, nie o godzinie 12∶32 -0500, użytkownik Mike Pagano
napisał:
> Upstream does not version patches and every change breaks the manifest
> which
> breaks the tree. This results in a constant chasing of bugs since we can't
> predict the breakage.
Shouldn't you also remove python-any-
Upstream does not version patches and every change breaks the manifest
which
breaks the tree. This results in a constant chasing of bugs since we can't
predict the breakage.
Signed-off-by: Mike Pagano
---
eclass/kernel-2.eclass | 102
+
1 file chan
