From: zimoun <zimon.toutoune@gmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: guix-science@gnu.org
Subject: Re: Help! I messed up guix-past
Date: Fri, 9 Sep 2022 17:46:46 +0200 [thread overview]
Message-ID: <CAJ3okZ0hohrWoLfLcXi2VrAiyK2xH6=cwwB9i=S6PbAfqdh+dw@mail.gmail.com> (raw)
In-Reply-To: <m1mtb87f3r.fsf@fastmail.net>
Hi Konrad,
On Fri, 9 Sept 2022 at 17:23, Konrad Hinsen <konrad.hinsen@fastmail.net> wrote:
> Two questions:
> - How can I fix this?
You cannot. Only a force push to overwrite the history removing your
unsigned commits. Well, IIUC. :-)
> - What should I have done to prevent this? Probably sign my commits,
> but is that enough? With nobody knowing my key, signing is probably not
> worth much on its own.
I think the manual has some answers.
https://guix.gnu.org/manual/devel/en/guix.html#Specifying-Channel-Authorizations
Cheers,
simon
next prev parent reply other threads:[~2022-09-09 15:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 15:16 Help! I messed up guix-past Konrad Hinsen
2022-09-09 15:36 ` Ricardo Wurmus
2022-09-09 15:46 ` zimoun [this message]
2022-09-09 16:10 ` Konrad Hinsen
2022-09-09 17:39 ` zimoun
2022-09-10 7:39 ` Konrad Hinsen
2022-09-10 9:47 ` zimoun
2022-09-10 16:20 ` Konrad Hinsen
2022-09-11 14:07 ` Ludovic Courtès
2022-09-11 15:19 ` Efraim Flashner
2022-09-12 6:16 ` Konrad Hinsen
2022-09-12 15:26 ` Ludovic Courtès
2022-09-13 8:58 ` Konrad Hinsen
2022-09-13 9:23 ` Ricardo Wurmus
2022-09-14 9:31 ` Konrad Hinsen
2022-09-10 10:27 ` Ludovic Courtès
2022-09-10 10:40 ` zimoun
2022-09-10 14:39 ` Ricardo Wurmus
2022-09-12 16:00 ` zimoun
2022-09-09 16:16 ` Julien Lepiller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ0hohrWoLfLcXi2VrAiyK2xH6=cwwB9i=S6PbAfqdh+dw@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-science@gnu.org \
--cc=konrad.hinsen@fastmail.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).