From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] heliotrope-syncback
Date: Wed, 09 Nov 2011 23:18:08 +0000 [thread overview]
Message-ID: <1320880426-sup-9891@masanjin.net> (raw)
In-Reply-To: <CAMiZLn3dsR_sRfpZV9MLKhJpVhfgsSpd6t3DwHDeg5uydY39Ow@mail.gmail.com>
Reformatted excerpts from Matthieu Rakotojaona's message of 2011-11-09:
> Okay, forget about buggy syncback, now comes the IMAP interface !
Now THIS is exciting. Thanks for starting on it!
> Considering the implementation, I've considered only UIDs, which are
> heliotrope's message_ids. Both can and must only go up as messages
> come and go, so it's cool.
That's right. Thread ids can sometimes be non-increasing, but message
ids should always be increasing. And the IMAP interface shouldn't have
anything to do with thread ids anyways.
> This leads me to the question : what is the license of Heliotrope ?
> Ximapd seems to be something BSD-like, but Heliotrope has none.
Hm, good question. I will probably GPL it. Let me think for a few days.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-11-09 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 23:55 Matthieu Rakotojaona
2011-11-07 6:57 ` William Morgan
2011-11-07 18:56 ` Michael Stapelberg
2011-11-09 3:22 ` Matthieu Rakotojaona
2011-11-09 23:18 ` William Morgan [this message]
2011-11-11 1:25 ` [sup-talk] " Matthieu Rakotojaona
2011-11-17 1:33 ` Matthieu Rakotojaona
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=1320880426-sup-9891@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@rubyforge.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