From: jdugan@es.net (Jon Dugan)
Subject: [sup-talk] sup traceback
Date: Wed, 07 May 2008 17:56:03 -0700 [thread overview]
Message-ID: <1210207992-sup-8093@junction.es.net> (raw)
In-Reply-To: <1210035536-sup-7502@south>
Excerpts from William Morgan's message of Mon May 05 17:59:55 -0700 2008:
> Interesting. Non-ASCII characters in a message id. Haven't seen that one
> before. Maybe I should SHA1 all message ids anyways.
Ayup, that made me do a double take too. I used mutt to delete it and ran a
sup-sync -c to get back to business. I kept a copy of the message if you want
to take a look, but the salient point was the wide chars in the message id.
Cheers,
Jon
--
Jon M. Dugan <jdugan at es.net> | GTalk: jdugan.esnet
ESnet Network Engineering Group | http://www.es.net
Lawrence Berkeley National Laboratory | http://www.lbl.gov/
next prev parent reply other threads:[~2008-05-08 0:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 18:19 Jon Dugan
2008-05-06 0:59 ` wmorgan-sup
2008-05-08 0:56 ` Jon Dugan [this message]
2008-05-11 23:20 ` William Morgan
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=1210207992-sup-8093@junction.es.net \
--to=jdugan@es.net \
/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