unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Should commit signing always be required for local work? [was Re: bug#63261: Recent changes to git config cause errors for non-committers]
Date: Fri, 19 May 2023 18:22:13 +0200	[thread overview]
Message-ID: <871qjcz3yi.fsf@gmail.com> (raw)
In-Reply-To: <877ct4r7f8.fsf@jpoiret.xyz>

Hi Josselin,

On ven., 19 mai 2023 at 11:34, Josselin Poiret <dev@jpoiret.xyz> wrote:

> I'm curious Leo, in general (not Guix because we have a pre-push hook),
> how do you make sure you always publish signed commits?  I don't want to
> put unsigned commits anywhere except locally, but it feels like I might
> just forget to sign them before pushing.

Well, I am not Leo. :-) Maybe I misunderstand your question but usually
my file ~/.gitconfig contains my default; say always sign.  Then
locally, for some project [1], I set other options with the local file
.git/config of the repository.

And for the ones I do not want to sign locally but I will push signed, I
have pre-push hooks.  Note, in practise, I do not have such
configuration. :-)

1: https://gitlab.inria.fr/guix-hpc/website


Cheers,
simon



  reply	other threads:[~2023-05-19 16:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874jospdr2.fsf@psyduck.jhoto.kublai.com>
     [not found] ` <87y1m024rx.fsf@gmail.com>
     [not found]   ` <ZF/fCxinkPg9lJNc@jasmine.lan>
     [not found]     ` <875y8tww86.fsf@gmail.com>
2023-05-18 16:59       ` Should commit signing always be required for local work? [was Re: bug#63261: Recent changes to git config cause errors for non-committers] Leo Famulari
2023-05-19  3:24         ` Maxim Cournoyer
2023-05-19  9:34           ` Josselin Poiret
2023-05-19 16:22             ` Simon Tournier [this message]
2023-05-24 21:00               ` Vagrant Cascadian
2023-05-24 21:17                 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-24 22:02                   ` Vagrant Cascadian
2023-05-26 17:54             ` Leo Famulari

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=871qjcz3yi.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=dev@jpoiret.xyz \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=maxim.cournoyer@gmail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).