From: ingmar.stdin@gmail.com (Ingmar Vanhassel)
Subject: [sup-talk] Backtrace with latest git
Date: Mon, 31 Dec 2007 02:00:39 +0100 [thread overview]
Message-ID: <1199062549-sup-2436@indigo> (raw)
Hello,
At the risk of boring you to pieces: "thanks for sup! :-)".
Finally a mail client that does what we want, how we want it.
As of latest git, I get a backtrace when I try to load more threads than
what the initial buffer shows. Backtrace attached.
Thanks,
Ingmar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sup-backtrace-20071231.log
Type: application/octet-stream
Size: 3990 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071231/7f881d0a/attachment.obj
next reply other threads:[~2007-12-31 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 1:00 Ingmar Vanhassel [this message]
2008-01-02 17:50 ` William Morgan
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=1199062549-sup-2436@indigo \
--to=ingmar.stdin@gmail.com \
/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