Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Adding hooks to sup-mail
Date: Mon, 23 May 2011 11:29:15 +0200	[thread overview]
Message-ID: <1306142903-sup-802@midna.zekjur.net> (raw)
In-Reply-To: <1305988436-sup-5041@jon-laptop>

Hi Jonathan,

Excerpts from Jonathan Ipser's message of 2011-05-21 16:49:59 +0200:
> registered on my system (see output below). None of these scripts are found
> in the location listed, however (the .sup/hooks directory is empty). Running
You should create these files :).

> Any information on how to add/modify hooks with sup-mail would be much
> appreciated. FYI, I installed sup-mail (v. 0.11) using the standard
> installation procedure for my Xubuntu OS. I am running sup-mail as the root
> user.   
You really shouldn’t run it as root, that’s dangerous.

Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

      reply	other threads:[~2011-05-23  9:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21 14:49 Jonathan Ipser
2011-05-23  9:29 ` Michael Stapelberg [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=1306142903-sup-802@midna.zekjur.net \
    --to=michael+sup@stapelberg.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