From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/2] remove more 40 char limits
Date: Tue, 15 Sep 2020 19:51:35 +0000 [thread overview]
Message-ID: <20200915195137.13476-1-e@80x24.org> (raw)
SHA-256 support is coming in git
Eric Wong (2):
mid: rename MID_MAX to ID_MAX
treewide: relax allow >=40 chars for git OID
lib/PublicInbox/Feed.pm | 4 ++--
lib/PublicInbox/Git.pm | 2 +-
lib/PublicInbox/Import.pm | 4 ++--
lib/PublicInbox/MID.pm | 4 ++--
lib/PublicInbox/ViewDiff.pm | 4 ++--
lib/PublicInbox/WWW.pm | 2 +-
t/edit.t | 4 ++--
t/plack.t | 2 +-
t/replace.t | 2 +-
t/v2writable.t | 4 ++--
10 files changed, 16 insertions(+), 16 deletions(-)
next reply other threads:[~2020-09-15 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 19:51 Eric Wong [this message]
2020-09-15 19:51 ` [PATCH 1/2] mid: rename MID_MAX to ID_MAX Eric Wong
2020-09-15 19:51 ` [PATCH 2/2] treewide: relax allow >=40 chars for git OID Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200915195137.13476-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.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).