From: Josh Marshall <joshua.r.marshall.1991@gmail.com>
To: Marius Bakke <marius@gnu.org>
Cc: 41345-done@debbugs.gnu.org
Subject: [bug#41345] 000-update-python-argon2-cffi.patch
Date: Sat, 30 May 2020 12:49:57 -0400 [thread overview]
Message-ID: <CAFkJGReRY6Fnq3YvBMa6qpcBHDqXxQV3=Nvt=9WWHb+zN54T9Q@mail.gmail.com> (raw)
In-Reply-To: <87k10t1s87.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
It could also enforce a number of linting details. That'd save reviewers
time.
On Sat, May 30, 2020, 09:12 Marius Bakke <marius@gnu.org> wrote:
> Josh Marshall <joshua.r.marshall.1991@gmail.com> writes:
>
> > If those are the particular expectations and standards, should they
> change
> > from only policy in the manual to something enforced by a git pre-commit
> > hook?
>
> That's a good idea. I'm not sure about enforcing, but we could have a
> post-commit hook that complains if all the files are not mentioned in
> the commit message.
>
[-- Attachment #2: Type: text/html, Size: 944 bytes --]
prev parent reply other threads:[~2020-05-30 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 4:20 [bug#41345] 000-update-python-argon2-cffi.patch Josh Marshall
2020-05-20 21:01 ` Marius Bakke
2020-05-20 21:07 ` Josh Marshall
2020-05-25 11:55 ` Josh Marshall
2020-05-25 14:59 ` bug#41345: 000-update-python-argon2-cffi.patch Marius Bakke
2020-05-25 16:13 ` [bug#41345] 000-update-python-argon2-cffi.patch Josh Marshall
2020-05-25 21:35 ` Marius Bakke
2020-05-25 22:39 ` Josh Marshall
2020-05-30 13:12 ` Marius Bakke
2020-05-30 16:49 ` Josh Marshall [this message]
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='CAFkJGReRY6Fnq3YvBMa6qpcBHDqXxQV3=Nvt=9WWHb+zN54T9Q@mail.gmail.com' \
--to=joshua.r.marshall.1991@gmail.com \
--cc=41345-done@debbugs.gnu.org \
--cc=marius@gnu.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/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).