From: Eric Wong <e@80x24.org>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
meta@public-inbox.org
Subject: Re: Bug related to (maybe?) / in Message-Id
Date: Tue, 7 Mar 2023 22:30:46 +0000 [thread overview]
Message-ID: <20230307223046.M658929@dcvr> (raw)
In-Reply-To: <20230307083159.M180016@dcvr>
Eric Wong <e@80x24.org> wrote:
> Thomas Weißschuh <thomas@t-8ch.de> wrote:
> > > # in file "msgid" next to muttrc
> > > # put any command within the backticks
> > > my_hdr Message-ID: <`uuidgen -r`@t-8ch.de>
>
> I didn't notice this earlier, but IMHO having Message-IDs
> prefixed with `%Y%m%d%H%M%S' can convey human-meaningful
> information in the URL without having to open the URL.
Btw, mutt may gain a more reasonable default:
https://marc.info/?i=20230307_213502_4a7Zc1MB@breakpoint.cc
(not sure how I feel about underscores, though)
(I brought this up a few years back, but wasn't successful:
https://marc.info/?i=20210110213922.iqTO594q5DM@dcvr )
prev parent reply other threads:[~2023-03-07 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 21:05 Bug related to (maybe?) / in Message-Id Uwe Kleine-König
2023-02-16 21:36 ` Eric Wong
2023-02-17 8:52 ` Uwe Kleine-König
2023-02-17 10:28 ` Eric Wong
2023-02-17 10:32 ` [PATCH] TODO: handle more cases of unencoded slashes Eric Wong
2023-02-17 11:08 ` [PATCH] public-inbox.cgi(1): Mention AllowEncodedSlashes for Apache setups Uwe Kleine-König
2023-02-17 13:15 ` Eric Wong
2023-02-18 17:58 ` Bug related to (maybe?) / in Message-Id Thomas Weißschuh
2023-02-18 18:06 ` Thomas Weißschuh
2023-03-07 8:31 ` Eric Wong
2023-03-07 22:30 ` Eric Wong [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://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=20230307223046.M658929@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=thomas@t-8ch.de \
--cc=u.kleine-koenig@pengutronix.de \
/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).