public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc(refs/meta/config)] Allow max-commit-emails to 500 for refactoring
Date: Tue, 29 Mar 2022 19:54:49 +0000 (GMT) [thread overview]
Message-ID: <20220329195449.105A13888C52@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b6371a9c4c406a3c5302544c595e797a749784c1
commit b6371a9c4c406a3c5302544c595e797a749784c1
Author: Carlos O'Donell <carlos@redhat.com>
Date: Tue Mar 29 15:54:29 2022 -0400
Allow max-commit-emails to 500 for refactoring
Diff:
---
project.config | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/project.config b/project.config
index 349bdde2db..4abfdb57c5 100644
--- a/project.config
+++ b/project.config
@@ -14,6 +14,11 @@
# We allow a 5MiB email diff maximum.
max-email-diff-size = 5242880
+ # We have had cases where we need 100 commits on a branch.
+ # We should allow more than 100 commits, so bumping this
+ # up to 500 should be sufficient.
+ max-commit-emails = 500
+
# Reject merge commits on a certain number of branches:
# - on master: We request that people rebase their changes
# before pushing instead (merge commits tend to confuse
reply other threads:[~2022-03-29 19:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220329195449.105A13888C52@sourceware.org \
--to=carlos@sourceware.org \
--cc=glibc-cvs@sourceware.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.
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).