From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: ulm@gentoo.org, arsen@aarsen.me, jporterbugs@gmail.com,
luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: Git snafu
Date: Wed, 26 Apr 2023 12:27:10 +0300 [thread overview]
Message-ID: <83y1mft2mp.fsf@gnu.org> (raw)
In-Reply-To: <87wn1zau6u.fsf@thaodan.de> (message from Björn Bidar on Wed, 26 Apr 2023 12:06:49 +0300)
> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: Ulrich Mueller <ulm@gentoo.org>, arsen@aarsen.me,
> jporterbugs@gmail.com, luangruo@yahoo.com, emacs-devel@gnu.org
> Date: Wed, 26 Apr 2023 12:06:49 +0300
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> But you'd catch errors due to bad configuration (as the one in question)
> >> where both author and committer tend to be wrong.
> >
> > How would we do that? The ACL to emacs.git is not available locally,
> > and neither should it be, IMO.
>
> You can block the commit in question with a post-receive hook I think.
On Savannah? Doesn't sound like a serious enough issue to ask
Savannah folks to install this.
next prev parent reply other threads:[~2023-04-26 9:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87a5ywcf1g.fsf.ref@yahoo.com>
2023-04-25 12:38 ` Git snafu Po Lu
2023-04-25 13:04 ` Eli Zaretskii
2023-04-25 13:13 ` Po Lu
2023-04-25 14:33 ` Dr. Arne Babenhauserheide
2023-04-25 14:43 ` Eli Zaretskii
2023-04-25 13:13 ` Robert Pluim
2023-04-25 13:37 ` Eli Zaretskii
2023-04-25 20:37 ` Jim Porter
2023-04-25 20:41 ` Arsen Arsenović
2023-04-26 5:44 ` Eli Zaretskii
2023-04-26 6:10 ` Ulrich Mueller
2023-04-26 6:42 ` Eli Zaretskii
2023-04-26 9:06 ` Björn Bidar
2023-04-26 9:27 ` Eli Zaretskii [this message]
2023-04-26 9:44 ` Arsen Arsenović
2023-04-26 0:44 ` Po Lu
2023-04-30 21:13 ` Jim Porter
2023-05-01 12:44 ` Eli Zaretskii
2023-05-01 16:44 ` Jim Porter
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y1mft2mp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arsen@aarsen.me \
--cc=bjorn.bidar@thaodan.de \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=luangruo@yahoo.com \
--cc=ulm@gentoo.org \
/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/emacs.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).