Re: [Replicant] Changes for 6.0 0004 release

Hi, On Sun, 23 Sep 2018 18:37:00 + Joonas Kylmälä wrote: > >> The 953d2a3493aaceb3209afc7eef1ff1e7f7242908 commit (Point > >> ResXMLTree to a copy of the asset buffer in > >> AssetManager::getPkgName()) was a fix for preventing devices from > >> ending in a boot loop when an application that

Re: [Replicant] Changes for 6.0 0004 release

Hi GNUtoo and others, Denis 'GNUtoo' Carikli: >> [0001-Revert-Point-ResXMLTree-to-a-copy-of-the-asset-buffe.patch > The commit reverted by the patch above is this one: >> commit 953d2a3493aaceb3209afc7eef1ff1e7f7242908 >> (replicant/replicant-6.0, m/replicant-6.0-dev) Author: Wolfgang >>

Re: [Replicant] Changes for 6.0 0004 release

Hey, Denis 'GNUtoo' Carikli: > On Sat, 15 Sep 2018 17:00:00 + > Joonas Kylmälä wrote: > >> I mean pushing those repositories where I did "git merge >> upstream/" and the merge worked without any conflicts >> and didn't require any additional commits after the merge. > ok, this looks good. >

Re: [Replicant] Changes for 6.0 0004 release

On Sat, 15 Sep 2018 17:00:00 + Joonas Kylmälä wrote: > I mean pushing those repositories where I did "git merge > upstream/" and the merge worked without any conflicts > and didn't require any additional commits after the merge. ok, this looks good. Acked-by: Denis 'GNUtoo' Carikli > I

Re: [Replicant] Changes for 6.0 0004 release

On Sat, 15 Sep 2018 17:43:00 + Joonas Kylmälä wrote: > Hi, Hi, > I have an image in my mind that maintaining patchwork for 58 or so git > repositories was difficult. If it doesn't turn out well there are > other options that we can try. Google was using Gerrit at least at > some point for

Re: [Replicant] Changes for 6.0 0004 release

Hi, Denis 'GNUtoo' Carikli: > On my side I should improve reviews time. I should also look into > installing a patchwork instance to keep track of the patches I forgot > about. I have an image in my mind that maintaining patchwork for 58 or so git repositories was difficult. If it doesn't turn

Re: [Replicant] Changes for 6.0 0004 release

Hi, thanks for taking a look! :) Denis 'GNUtoo' Carikli: >> I can start pushing the merged repositories that didn't require any >> additional commits to make it work. Is that fine? > I don't understand what that means. I mean pushing those repositories where I did "git merge upstream/" and the

Re: [Replicant] Changes for 6.0 0004 release

On Tue, 28 Aug 2018 17:23:00 + Joonas Kylmälä wrote: > Hi, Hi, > I have made bunch of little modifications to merge latest updates and > security fixes from upstream sources for the next Replicant 6.0 0004 > release. Thanks for working on this. > Please review them: On my side I should

Re: [Replicant] Changes for 6.0 0004 release

On Sun, 02 Sep 2018 19:07:00 + Joonas Kylmälä wrote: > Hi, Sorry for the delay, I thought that I already sent this mail but it was stuck in my draft folder as I was interrupted and didn't finish writing it. > I can start pushing the merged repositories that didn't require any > additional

Re: [Replicant] Changes for 6.0 0004 release

Hi, just a gentle reminder: if you have time it would be great if you could take a look at the patches so we can get this moving forward. Joonas Joonas Kylmälä: > Hi, > > I can start pushing the merged repositories that didn't require any > additional commits to make it work. Is that fine? >

Re: [Replicant] Changes for 6.0 0004 release

Hi, I can start pushing the merged repositories that didn't require any additional commits to make it work. Is that fine? I would also still like some feedback on the patches I sent earlier and won't be pushing them before someone comments on them. There has been one patch more created for