portato - Portato - A Portage GUI

	Commit message (Expand)	Author	Age	Files	Lines
*	added etcproposals-1.2 support	necoro	2007-05-09	1	-2/+29
*	removed highlight plugin from normal portato	necoro	2007-04-26	1	-33/+0
*	highlight works -> reverting to old	necoro	2007-04-26	1	-1/+1
*	trying the new gtksourceview	necoro	2007-04-26	1	-1/+1
*	added noroot-option	necoro	2007-04-25	2	-4/+21
*	Made qt plugin-ready; lots of documentation	necoro	2007-04-20	1	-5/+3
*	Some small changes for etcproposals 1.1	necoro	2007-03-31	1	-2/+2
*	Some small changes for etcproposals 1.1	necoro	2007-03-31	1	-2/+2
*	Some small changes for etcproposals 1.1	necoro	2007-03-31	1	-6/+13
*	Allowed Plugins to have a menu	necoro	2007-03-31	1	-3/+11
*	Added etc-proposals plugin	necoro	2007-03-15	1	-0/+35
*	First plugin support	necoro	2007-03-10	2	-0/+44

/others/feed2imap.git/commit/lib/feed2imap/maildir.rb?id=94dc1db641f98242496a32409e823920f4e700e9&follow=1'>Patch to use feed item pubDate in Maildir file namesBernie Maier1-6/+10 Hi! I've just subscribed to the list, having downloaded feed2imap a few days ago. Since I want to just write RSS feeds to a local Maildir, this looked like just what I needed. Unfortunately, the release 1.0 version seems to randomise the order of the feed items when doing the first fetch for a new feed. Looking at maildir.rb, there is a "TODO: handle `date'" comment and it looks like the code is just generating maildir filenames using the timestamp at the time the items are being written into the maildir. Since all the initial items are written at the same time, and the maildir file name has a random element, this loses the original ordering from the mail feed. The solution is to use the timestamp corresponding to the pubDate in the feed item as the initial component of the maildir file name. Also, instead of using a random integer to force uniqueness in the second component of the file name, I think it is better to use a sequence number for each feed item, which will still be unique for the feed and also preserve item order. My patch follows (it's the first piece of Ruby code I've ever written / modified)... Cheers, Bernie 2010-04-18update websiteLucas Nussbaum2-2/+15 2010-04-18prepare releaseLucas Nussbaum4-5/+5 2010-04-18provide a way to disable SSL certificate verificationLucas Nussbaum4-1/+12 2010-04-18update changelogLucas Nussbaum1-0/+4 2010-04-18Update rubyimap.rbLucas Nussbaum1-5/+38 Update rubyimap.rb to upstream revision 27336 2010-03-17Document the maildir targetSandra Snan3-5/+5 I looked for a good feed to maildir program, and I couldn’t find one. Turns out, by looking at feed2imaps source code, that it has that function. So here’s a documentation patch so it’s easier to find. This patch shouldn’t touch any code. Generated by git. Sandra Signed-off-by: Sandra Snan <sandra.snan@handgranat.org> 2009-12-26Avoid using "acme.com"Lucas Nussbaum4-10/+19 Patch from Guido Berhoerster <guido@berhoerster.name>: Hello, here is a small patch that avoids using the valid(!) domain "acme.com" for generating message ids and email addresses. It adds a new global configuration option "default-email" which will be used in case a feed does provide one, currently feed2imap resorts to "feed2imap@acme.com". If this configuration option is not given it will basically default to <logname>@<hostname> as returned by Etc.getlogin and Socket.gethostname. Yours, 2009-09-04fix to use Message-Id instead of X-CacheIndexLucas Nussbaum1-5/+2 2009-09-03added the forth arg to ConfigFeed::new for maildirLucas Nussbaum1-1/+1