Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Tero Tilus <tero@tilus.net>
To: anonymous <sup-bugs@masanjin.net>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [issue64] Crash on sup start
Date: Tue, 09 Feb 2010 09:41:31 +0200	[thread overview]
Message-ID: <1265701233-sup-895@tilus.net> (raw)
In-Reply-To: <1265688194.03.0.035958787068.issue64@masanjin.net>

Sorry, I replied using mail before I checked further messages in this
tracker.

Could you be able to identify the offending docid and maybe the
mail(s) that docid points to?  Just to get a hint on what happened.
Hit ~ to get console buffer where you can play just like in
devel/console.sh, see
<http://sup.rubyforge.org/wiki/wiki.pl?ProgrammaticallyAccessingSupsIndex>

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  parent reply	other threads:[~2010-02-09  7:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09  4:03 anonymous
2010-02-09  7:16 ` Tero Tilus
2010-02-09  7:41 ` Tero Tilus [this message]
2010-08-24 21:21 ` Gaute Hope

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=1265701233-sup-895@tilus.net \
    --to=tero@tilus.net \
    --cc=sup-bugs@masanjin.net \
    --cc=sup-devel@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