From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] Now in master: multiple-locations and remote-source-removal
Date: Sat, 03 Apr 2010 14:01:56 -0400 [thread overview]
Message-ID: <1270316637-sup-2831@zyrg.net> (raw)
As promised, IMAP and mbox+ssh sources have been completely removed from
the codebase.
I've also merged the index format change to keep track of all locations
(source + source_info) for a message. Once you've opened your index with
an upgraded sup you won't be able to read it with an older sup. I expect
the multiple-locations change by itself to be stable so that shouldn't
be a big deal. It is important to get it in master before I merge the
maildir branch to next so that you can switch between them without
nuking your index.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
reply other threads:[~2010-04-03 18:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1270316637-sup-2831@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--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