On 4/13/24 05:47, Giovanni Biscuolo wrote:
> Hello Skyler,
>
> Skyler Ferris writes:
>
>> On 4/12/24 23:50, Giovanni Biscuolo wrote:
>>> general reminder: please remember the specific scope of this (sub)thread
> [...]
>
>>> (https:
Hi all,
On 4/11/24 06:49, Andreas Enge wrote:
> Am Thu, Apr 11, 2024 at 02:56:24PM +0200 schrieb Ekaitz Zarraga:
>> I think it's just better to
>> obtain the exact same code that is easy to find
> The exact same code as what? Actually I often wonder when looking for
> a project and end up with a
evant to what to
currently/could possibly do. Please let me know if you think that this
is incorrect.
Additionally, I need to correct something that I previously said. I
stated this:
On 4/12/24 17:14, Skyler Ferris wrote:
> even the tails project gets this part of security wrong and they are
>
On 3/12/24 13:45, Peter Polidoro wrote:
> If I remember correctly, that was a patch I submitted a couple of years ago
> when I was attempting to package some embedded software tools, either the
> zephyr west tool or platformio, both written in python. That sent me down the
> rabbit hole of
Hello,
I am looking through the [backlog of open patch
submissions](https://issues.guix.gnu.org/search?query=is%3Aopen+tag%3Apatch) to
see if any are actionable on my end. One such patch is [issue 55728 which
updates python-mock](https://issues.guix.gnu.org/55728). Based on the output of
On 2/6/24 05:39, Steve George wrote:
> I agreed to organise some 'patch review' online sessions in the next couple of
> weeks.
>
> Organising a basic process is a good topic for that online session. For
> example, elsewhere in the thread someone mentions some tags we could use
> consistently so
Hello,
I am writing to see if the project is interested in using an updated version of
kmscon. I ran across this information because I have started using kmscon as
the main interface on my Guix machine, and ended up digging into it a bit. I am
sending this email only because I think it is
