From: ezyang@MIT.EDU (Edward Z. Yang)
Subject: [sup-talk] Odd bug with lazy-loaded messages
Date: Sun, 09 Aug 2009 04:40:33 -0400 [thread overview]
Message-ID: <1249807206-sup-55@javelin> (raw)
In-Reply-To: <1249711570-sup-2277@javelin>
Excerpts from Edward Z. Yang's message of Sat Aug 08 02:07:22 -0400 2009:
> Great. I sprinkled a few extra load_from_source! calls and I think
> I made the weird behavior go away. It's kind of sketchy though.
It looks like it's still a problem in some sporadic cases. Going to
submit a more thorough patch soon.
Cheers,
Edward
next prev parent reply other threads:[~2009-08-09 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 17:36 Edward Z. Yang
2009-08-03 17:18 ` William Morgan
2009-08-08 6:07 ` Edward Z. Yang
2009-08-09 8:40 ` Edward Z. Yang [this message]
2009-12-15 22:40 ` Edward Z. Yang
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=1249807206-sup-55@javelin \
--to=ezyang@mit.edu \
/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