From: ian@lorf.org (Ian Taylor)
Subject: [sup-talk] no message-id field in header
Date: Tue, 12 Jun 2007 14:20:13 -0400 [thread overview]
Message-ID: <1181671858-sup-239@zap> (raw)
When doing...
sup-sync -c
...I see lots of messages about ignoring erroneous messages missing the
message-id field.
These messages are the same that seem to be ignored by sup.
I really like sup, but I can't rely on it right now because of this. I'm
using latest subversion.
next reply other threads:[~2007-06-12 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 18:20 Ian Taylor [this message]
2007-06-13 0:07 ` William Morgan
2007-06-13 0:42 ` Brian
2007-06-13 2:08 ` Ian Taylor
2007-06-13 2:11 ` William Morgan
2007-06-13 2:32 ` Brian
2007-06-13 18:04 ` 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=1181671858-sup-239@zap \
--to=ian@lorf.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