From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] current state of synching upstream?
Date: Tue, 21 Dec 2010 13:01:59 +0200 [thread overview]
Message-ID: <1292929122-sup-7072@tilus.net> (raw)
In-Reply-To: <20101221064445.GZ60419@icsi.berkeley.edu>
Matthias Vallentin, 2010-12-21 08:44:
>> The only downside to this is that my sources.yaml file needs manual
>> twiddling at restart to add the sources that were added during
>> runtime.
>
> As Tero mentioned, this is weird indeed since sup calls Index.save
> which in turn should call SourceManager.save_sources. I'll look into
> this when I get a chance.
...
> Neither master nor Damien's Maildir clone contain the class
> Recoverable. Is this code you added somewhere else?
This sources not getting saved might be because of that Recoverable
wrapper class. YAML marshalling might not be able to digest it.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-12-21 11:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 9:40 Ryan Barrett
2010-04-11 17:52 ` Ryan Barrett
2010-04-12 0:57 ` Rich Lane
2010-04-12 5:02 ` Andrew Pimlott
2010-04-12 12:11 ` Daemian Mack
2010-04-12 9:53 ` Tero Tilus
2010-04-14 13:00 ` William Morgan
2010-04-14 14:16 ` Ben Walton
2010-04-14 15:57 ` William Morgan
2010-04-14 16:08 ` Ben Walton
2010-12-15 8:19 ` Matthias Vallentin
2010-12-15 17:06 ` James Taylor
2010-12-18 5:12 ` Matthias Vallentin
2010-12-18 5:25 ` James Taylor
2010-12-18 19:04 ` Matthias Vallentin
2010-12-18 19:21 ` Ben Walton
2010-12-18 20:02 ` Tero Tilus
2010-12-18 20:12 ` Ben Walton
2010-12-21 6:44 ` Matthias Vallentin
2010-12-21 6:48 ` Matthias Vallentin
2010-12-21 11:01 ` Tero Tilus [this message]
2010-12-21 14:11 ` Ben Walton
2010-12-22 14:42 ` Matthias Vallentin
2010-12-22 16:27 ` Tero Tilus
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=1292929122-sup-7072@tilus.net \
--to=tero@tilus.net \
--cc=sup-talk@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