[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Tricking peer review
From: |
Ryan Prior |
Subject: |
Re: Tricking peer review |
Date: |
Fri, 15 Oct 2021 22:28:26 +0000 |
On Friday, October 15th, 2021 at 10:03 PM, Liliana Marie Prikler
<liliana.prikler@gmail.com> wrote:
> > On the plus side, such an attack would be recorded forever in Git
> >
> > history.
>
> On the minus side, time-machine makes said record a landmine to step
>
> into.
I've suggested this before and this seems like a good time to bring it up
again: can we create a database of known "bad" Guix commit hashes, and make
time-machine fetch the list and warn before it'll visit one of those hashes?
This would resolve the land-mine problem and generally de-risk our git tree,
which is maintained by fallible volunteers who will occasionally push tragic
commits.
- Tricking peer review, Ludovic Courtès, 2021/10/15
- Re: Tricking peer review, Liliana Marie Prikler, 2021/10/15
- Re: Tricking peer review,
Ryan Prior <=
- Re: Tricking peer review, Ludovic Courtès, 2021/10/18
- Re: Tricking peer review, Ryan Prior, 2021/10/18
- Re: Tricking peer review, zimoun, 2021/10/19
- Re: Tricking peer review, Leo Famulari, 2021/10/20
- Re: Tricking peer review, zimoun, 2021/10/21
Re: Tricking peer review, Thiago Jung Bauermann, 2021/10/15
Re: Tricking peer review, Ludovic Courtès, 2021/10/18