[Replicant] Building Android 10

[Denis 'GNUtoo' Carikli]

On Fri, 26 Jun 2020 13:37:31 +0200
Tobias Tefke <t.tefke at stud.fh-sm.de> wrote:

> Hi,
Hi,

> First of all, thank you for your answers.
> 
> I reworked the commit messages of the patches (all new patches can be 
> found in the attachments).
Thanks a lot for the patches. I've reworked a tiny bit some parts of the
commit messages and I've also pushed them all.

> Concerning the patch for i9300 inheriting wrongly from LineageOS:
> 
> I reworked the patch I sent last same. As Denis pointed out, this has 
> been already fixed in Replicant 9, which I did not notice until he 
> replied to my message in which I proposed a patch for that. I added
> this background information to that patch, thank you for letting me
> know.
The bug wasn't fixed in Replicant 9 but in a 'modem' branch. I've added
more information in the commit message (hoping that my description is
clear enough) as it is very useful:
- I was practically speaking the only one with that information, and
  that it may be useful later.
- It's generally useful to find which commit introduced a bug as this
  makes people's work much easier: If you are trying to find which
  commit introduced a bug, for instance you have a totally red screen,
  and you need to find which commit introduced it to fix it, but
  while going back to the old git revisions you have an unrelated bug
  that prevents you from booting the device, then with information on
  which commit introduced which bug and which commit fixes that, you 
  have everything you need to know to fix it without needing to re-do
  all the work.
  So you can then rework the git history to remove that booting
  bug completely and only focus on the red screen bug.
  Generally speaking it also helps a lot distributions backporting
  fixes as you know what patches you need to apply to fix specific bugs.
- It's also very interesting to understand how I managed to create that
  bug (in order to avoid future similar bugs).

> in this mail I'm replying to the answers I got to my most recent
> mailing list submission (published in Replicant Digest Vol 359 Issue
This is because when you registered to the Replicant mailing list, you
chose the "Digest" option, and the subscription web interface doesn't
explain anywhere the consequences of that choice.

While this options makes following a mailing list easier for some
people, it typically makes it extremely hard to participate in
conversations as you don't receive individuals mails anymore, but a big
mail with all the other mails inside.

And for some reason mail clients don't know how to deal with that as
they either expect the mail to follow the RFC that defines the mail
format, or don't have the information that they need to reply to the
mails (like the Reference ID).

The most simple way to fix it is to request your password by mail if you
don't already have one or that you forgot it, and changing your
"Digest" settings to "No", in this web interface:
https://lists.osuosl.org/mailman/listinfo/replicant

Denis.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osuosl.org/pipermail/replicant/attachments/20200626/b01b46fa/attachment.asc>