From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] EOFError crash
Date: Thu, 06 Nov 2008 22:21:06 -0800 [thread overview]
Message-ID: <1226038806-sup-9313@entry> (raw)
In-Reply-To: <1226025882-sup-6197@blackpad>
Reformatted excerpts from Eduardo Habkost's message of 2008-11-06:
> Just tried it (commit 6831c5966aa0a6021978bffc071734d03cabf2b1).
>
> Triggered the same kind of exceptions of before (two samples below),
> when pressing P and M multiple times quickly on inbox-mode, followed by
> pressing 'end' and 'j'.
Interesting. I can't reproduce this on my end.
Can you please try commit d66cbee, which you can find if you check out
the 'index-locking' branch?
Thanks for helping me test this!
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-11-07 6:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 18:42 Decklin Foster
2008-11-02 17:40 ` Decklin Foster
2008-11-05 17:48 ` William Morgan
2008-11-06 14:33 ` Eduardo Habkost
2008-11-06 15:06 ` Nicolas Pouillard
2008-11-06 21:40 ` William Morgan
2008-11-07 2:52 ` Eduardo Habkost
2008-11-07 6:21 ` William Morgan [this message]
2008-11-07 11:32 ` Eduardo Habkost
2008-11-07 13:08 ` Eduardo Habkost
2008-11-10 3:59 ` 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=1226038806-sup-9313@entry \
--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