From: Joseph Myers <joseph@codesourcery.com>
To: Mike FABIAN <mfabian@redhat.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [Patch 1/13] [BZ #14095] update collation data from Unicode / ISO 14651
Date: Fri, 26 Jan 2018 15:49:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1801261313530.14878@digraph.polyomino.org.uk> (raw)
In-Reply-To: <s9dd11wnaia.fsf@taka.site>
Patches 1 and 12 have appeared on the mailing list multiple times
(different ezmlm sequence numbers; only once in the list archives because
those remove duplicates by message-id). Is there some email system
problem here (sending system timing out and resending the message,
receiving system accepting it multiple times)?
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-01-26 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 11:14 Mike FABIAN
2018-01-26 12:17 ` Mike FABIAN
2018-01-26 12:26 ` Mike FABIAN
2018-01-26 15:49 ` Joseph Myers [this message]
2018-01-26 17:07 ` Mike FABIAN
2018-01-26 21:10 ` Joseph Myers
2018-01-27 15:56 ` Mike FABIAN
2018-01-27 3:58 ` Carlos O'Donell
2018-01-27 16:04 ` Mike FABIAN
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=alpine.DEB.2.20.1801261313530.14878@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=mfabian@redhat.com \
/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).