From: pierre@baillet.name (Pierre Baillet)
Subject: [sup-talk] sup-sync-back: killed threads and read status
Date: Mon, 15 Oct 2007 08:02:12 +0200 [thread overview]
Message-ID: <6205b42d0710142302u2ca4c6c0yc53336434bc4fe39@mail.gmail.com> (raw)
Hi,
sup-sync-back does not seem to delete killed messages. I think, it should do
that.
Moreover, the "Read" status of emails is not changed in the original
mailbox. I'm not sure it's sup-sync-back job to do that, but the Principle
Of Least Surprise would probably expect that.
Cheers,
--
Pierre Baillet <pierre at baillet.name>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/sup-talk/attachments/20071015/b0db3b0b/attachment.html
next reply other threads:[~2007-10-15 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 6:02 Pierre Baillet [this message]
2007-10-15 6:42 ` Christopher Warrington
2007-10-29 15:46 ` 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=6205b42d0710142302u2ca4c6c0yc53336434bc4fe39@mail.gmail.com \
--to=pierre@baillet.name \
/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