From: Hamish D <dmishd@gmail.com>
To: William Morgan <wmorgan-sup@masanjin.net>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] problem starting sup
Date: Sun, 30 Jan 2011 23:07:02 +0000 [thread overview]
Message-ID: <AANLkTi=eZojPJvMB4=AqWPm_MhyvhCoa5Qfq3bNCm+rm@mail.gmail.com> (raw)
In-Reply-To: <1296093042-sup-322@masanjin.net>
> Initting the hookmanager happens very early on in Sup, so I'm guessing
> there's something wrong with your config file or the log file (the only
> two things that happen before the hookmanager is brought up).
I moved .sup out of the way and the error went away. Then with playing
with it I managed to delete the .sup directory that caused the errors
:/ If I ever happen to reproduce this I'll know what to do anyway.
Hamish
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-01-30 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 23:59 Hamish D
2011-01-27 0:24 ` Marc Weber
2011-01-27 1:57 ` William Morgan
2011-01-30 23:07 ` Hamish D [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='AANLkTi=eZojPJvMB4=AqWPm_MhyvhCoa5Qfq3bNCm+rm@mail.gmail.com' \
--to=dmishd@gmail.com \
--cc=sup-talk@rubyforge.org \
--cc=wmorgan-sup@masanjin.net \
/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