Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Gaute Hope <eg@gaute.vetsj.com>
To: Jonathan Lassoff <jof@thejof.com>
Cc: Hamish D <dmishd@gmail.com>, sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup: Fix for an UndefinedMethodError
Date: Sat, 13 Apr 2013 15:17:37 +0200	[thread overview]
Message-ID: <51695AF1.2070701@gaute.vetsj.com> (raw)
In-Reply-To: <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>

On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>> Hi,
>>
>> Jonathan: I put your commit into a pull request at:
>> - https://github.com/sup-heliotrope/sup/pull/19
>>
>> Also, re-branding and updating to web-references:
>> - https://github.com/sup-heliotrope/sup/pull/20
>>
>> any comments on this? You can see the changes I made. I have absolutely
>> no intentions of stepping on any toes, but this is a suggestion.
>
> No, thank you very much! That looks great!
>
>> It is a pity that the official home page and probably first search
>> results direct to the abandoned home and gem of sup.
>
> It is too bad. Hopefully William could hand off access or at least
> push updates somehow.
>
> If not, maybe we could stand up another domain pointing to github pages?
> Looks like supmua.org and supm.ua are available. :p
>
> --j

Yeah.. I think some web page is pretty essential, perhaps just the 
standard github-pages domain for a start. Anyone feel up for the task, 
I'd be happy to add you to the github-organization.

Regards, Gaute



  reply	other threads:[~2013-04-13 13:18 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 [this message]
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

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=51695AF1.2070701@gaute.vetsj.com \
    --to=eg@gaute.vetsj.com \
    --cc=dmishd@gmail.com \
    --cc=jof@thejof.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