From: Eli Zaretskii <eliz@gnu.org>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: jporterbugs@gmail.com, luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: Git snafu
Date: Wed, 26 Apr 2023 08:44:13 +0300 [thread overview]
Message-ID: <83edo7uriq.fsf@gnu.org> (raw)
In-Reply-To: <86cz3rheta.fsf@aarsen.me> (message from Arsen Arsenović on Tue, 25 Apr 2023 22:41:27 +0200)
> From: Arsen Arsenović <arsen@aarsen.me>
> Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
> Date: Tue, 25 Apr 2023 22:41:27 +0200
>
> It might be viable to compare the committer against the ACLs for
> emacs.git or such. The authors can vary widely, but the committer
> should usually be somebody that can write to the repository.
But the committer's name, as recorded in the Git logs, is really of no
special interest to us. Only the author's name and email address are
of interest. The access rights to the Git repository are checked by
Savannah, and if the commit was successfully pushed, that check
succeeded, regardless of what's in the log.
next prev parent reply other threads:[~2023-04-26 5:44 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83edo7uriq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arsen@aarsen.me \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=luangruo@yahoo.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.