From: Ruthard Baudach <ruthard.baudach@web.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Hooks - some examples appreciated
Date: Fri, 30 Nov 2012 09:49:34 +0100 [thread overview]
Message-ID: <1354264971-sup-7791@prxbdc.dyndns.org> (raw)
In-Reply-To: <CAMiZLn19MB=DMY_e7NMqMapzStLuq7vUV-jxy1J7iAiTLwAN3w@mail.gmail.com>
>== Auszüge aus der Nachricht von Matthieu Rakotojaona vom 2012-11-27 18:48:
> On Tue, Nov 27, 2012 at 4:13 PM, Ruthard Baudach <ruthard.baudach@web.de>wrote:
>
> > A first important point would be a central source of information like
> > the sup-wiki, but with spam-protection.
> >
>
> I started a brief API overview on my github branch :
> https://github.com/rakoo/heliotrope/wiki
Good work, -- but necessary for developers, not for users.
This is the main problem with heliotrope/turnsole -- it's yet not
suitable for (advanced) users. I know enough ruby to adapt hook scripts
for my needs, but do not have time to learn ruby by heart, or to
participate in the development of heliotrope/turnsole. I tried to
install it two or three times, but didn't manage to.
Regards
Ruthard
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2012-11-30 9:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 14:54 Andre Tann
2012-11-22 21:35 ` Jim Cheetham
2012-11-23 11:16 ` Andre Tann
2012-11-23 15:14 ` Ruthard Baudach
2012-11-23 18:49 ` Steven Hum
2012-11-23 20:20 ` Andre Tann
2012-11-25 21:09 ` Jim Cheetham
2012-11-27 12:54 ` Matthieu Rakotojaona
2012-11-27 15:13 ` Ruthard Baudach
2012-11-27 17:48 ` Matthieu Rakotojaona
2012-11-30 8:49 ` Ruthard Baudach [this message]
2012-11-24 20:42 ` Andre Tann
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=1354264971-sup-7791@prxbdc.dyndns.org \
--to=ruthard.baudach@web.de \
--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