On 2017-09-06 17:17, [ext] Andreas Reichel wrote: > On Wed, Sep 06, 2017 at 12:31:38PM +0200, Claudius Heine wrote: >> >> >> On 09/05/2017 10:27 AM, [ext] Andreas Reichel wrote: >>> From: Reichel Andreas <[email protected]> >>> >>> - the introduction of a special marker byte which tells the algorithm >>> - to not touch the original content. Deletion of user variables led to >>> - another special case, where *negative* variables had to be defined by >>> - a special `DELETED` type to tell the algorithm that the specific user >>> - variable has to be deleted. This is rather complicated and a better >>> - aproach has already been discussed using a journal with actions >>> - instead of a prebuilt state. >> >> I am not sure if TODO files in a repo is the best way forward. Maybe rather >> use issues on github for this? >> > If Jan agrees, we can move to github issues after this file is empty.
We could also use github issues if they are considered reminders, not discussion threads. That has to be made clear. Jan -- Siemens AG, Corporate Technology, CT RDA ITP SES-DE Corporate Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/ca0b4111-d00e-3345-5d10-f6af16b41958%40siemens.com. For more options, visit https://groups.google.com/d/optout.
