From: Jonathan Lassoff <jof@thejof.com>
To: Hamish D <dmishd@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup: Fix for an UndefinedMethodError
Date: Sat, 13 Apr 2013 03:06:21 -0700 [thread overview]
Message-ID: <CAHsqw9vwUsq6AmT9FUanxWuDgoAgHTdq-29cMN8hseZwEyN=6g@mail.gmail.com> (raw)
In-Reply-To: <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
On Fri, Apr 12, 2013 at 12:46 PM, Hamish D <dmishd@gmail.com> wrote:
> We've set up https://github.com/sup-heliotrope/sup
>
> Please feel free to put pull requests up there. And contributions to the new
> wiki are also very welcome. We have lots of missing pages ...
>
> https://github.com/sup-heliotrope/sup/wiki
Hey -- that's a most excellent place to put a wiki up. Glad to find
where the action's at.
> We have emailed William about this but have had no response. So currently we
> have no access to publishing gems under the sup name.
>
> As to a meet up, I'm in England so won't be coming to San Francisco :-P
Oh no worries, I just mention it because I know WIlliam is from
somewhere around here. I think he's working in SF now.
>> I'm very sorry. It seems that an error occurred in Sup. Please
>> accept my sincere apologies. Please submit the contents of
>> /home/jof/.sup/exception-log.txt and a brief report of the
>> circumstances to http://masanjin.net/sup-bugs/ so that I might
>> address this problem. Thank you!
>>
>> Sincerely,
>> William
>
> We should update this text ...
>
> Hamish
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2013-04-13 10:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 18:09 Jonathan Lassoff
2013-04-12 18:46 ` Steven Hum
2013-04-12 19:46 ` Hamish D
2013-04-13 9:16 ` Gaute Hope
2013-04-13 10:09 ` Jonathan Lassoff
2013-04-13 13:17 ` Gaute Hope
2013-04-13 16:35 ` Jonathan Lassoff
2013-04-13 17:14 ` Gaute Hope
2013-04-13 17:37 ` Gaute Hope
2013-04-13 19:19 ` Jonathan Lassoff
2013-04-13 20:48 ` Jonathan Lassoff
2013-04-13 22:17 ` Gaute Hope
2013-04-14 11:31 ` [sup-devel] " Eric Weikl
2013-04-14 12:05 ` Gaute Hope
2013-04-14 17:39 ` Eric Weikl
2013-04-16 20:30 ` [sup-talk] [sup-devel] " Eric Weikl
2013-04-16 21:21 ` Matthieu Rakotojaona
2013-04-17 8:51 ` Gaute Hope
2013-04-17 3:31 ` Steven Hum
2013-08-15 13:22 ` [sup-devel] Is maildir-sync ready for prime time? Eric Weikl
2013-08-15 13:35 ` [sup-talk] " Steven Schmeiser
2013-04-14 17:45 ` [sup-talk] sup: Fix for an UndefinedMethodError Hamish D
2013-04-14 22:32 ` Gaute Hope
2013-04-15 11:42 ` Gaute Hope
2013-04-13 19:15 ` Jonathan Lassoff
2013-04-13 22:20 ` Gaute Hope
2013-04-13 12:49 ` Matthieu Rakotojaona
2013-04-13 13:29 ` Gaute Hope
2013-04-13 15:42 ` Steven Hum
2013-04-13 10:06 ` Jonathan Lassoff [this message]
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='CAHsqw9vwUsq6AmT9FUanxWuDgoAgHTdq-29cMN8hseZwEyN=6g@mail.gmail.com' \
--to=jof@thejof.com \
--cc=dmishd@gmail.com \
--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