From: Paul Eggert <eggert@cs.ucla.edu>
To: Stanley Lancaster <lancasterharp@gmail.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] Update to %Z fix
Date: Mon, 24 Jul 2023 09:48:12 -0700 [thread overview]
Message-ID: <4b07d9d6-9d1a-8527-768b-ebe72f9e5ec1@cs.ucla.edu> (raw)
In-Reply-To: <20230724135321.12195-1-lancasterharp@gmail.com>
The indenting is so messed up on that one that I found it hard to read.
To help keep track of patch versions, please use the same subject line
except say [PATCH v3], [PATCH v4] etc.
prev parent reply other threads:[~2023-07-24 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 14:52 Fix %Z parsing in strptime [BZ #16088] Stanley Lancaster
2023-07-14 16:11 ` Paul Eggert
2023-07-18 17:17 ` Stanley Lancaster
2023-07-18 17:22 ` Stanley Lancaster
2023-07-19 2:13 ` Paul Eggert
2023-07-24 13:53 ` [PATCH] Update to %Z fix Stanley Lancaster
2023-07-24 16:48 ` Paul Eggert [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4b07d9d6-9d1a-8527-768b-ebe72f9e5ec1@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=lancasterharp@gmail.com \
--cc=libc-alpha@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).