From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Backtrace with latest git
Date: Wed, 02 Jan 2008 09:50:39 -0800 [thread overview]
Message-ID: <1199296151-sup-713@south> (raw)
In-Reply-To: <1199062549-sup-2436@indigo>
[completely faking this reply because my ISP dropped most of my email
over the last few days... sigh.]
Ingmar Vanhassel wrote:
> At the risk of boring you to pieces: "thanks for sup! :-)". Finally a
> mail client that does what we want, how we want it.
Thanks, it's always good to hear.
> As of latest git, I get a backtrace when I try to load more threads
> than what the initial buffer shows. Backtrace attached.
This should be fixed in git. Let me know if not.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-01-02 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 1:00 Ingmar Vanhassel
2008-01-02 17:50 ` William Morgan [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=1199296151-sup-713@south \
--to=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