From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Initial import does not preserve read/unread status
Date: Tue, 12 Aug 2008 20:14:09 -0700 [thread overview]
Message-ID: <1218597196-sup-3699@entry> (raw)
In-Reply-To: <20080810235352.GA20706@thened.net>
Reformatted excerpts from Alec Berryman's message of 2008-08-10:
> When I imported a new maildir source with a mix of read and unread
> messages (in the cur or new subfolder, respectively), all of the
> messages were marked unread. Is the documentation wrong or is this a
> bug? I hope it's a bug.
Weird. Can you provide some sample filenames for read and unread
messages? (Since that's how Maildir keeps state---it might be there's
some naming variant that Sup doesn't know about.)
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-08-13 3:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 23:53 Alec Berryman
2008-08-11 0:13 ` Alec Berryman
2008-08-13 3:14 ` William Morgan [this message]
2008-08-17 18:59 ` Alec Berryman
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=1218597196-sup-3699@entry \
--to=wmorgan-sup@masanjin.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