From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: Ben Walton <bwalton@artsci.utoronto.ca>,
sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Behavior for sent messages
Date: Thu, 09 Sep 2010 12:56:11 -0400 [thread overview]
Message-ID: <1284051347-sup-9359@ezyang> (raw)
In-Reply-To: <1281916596-sup-8793@ezyang>
Excerpts from Edward Z. Yang's message of Sun Aug 15 19:58:03 -0400 2010:
> I've tracked down the regression to this merge: 45c3433c0 Merge remote branch 'origin/maildir'
>
> I'd appreciate a quick san-check before I start investigating the merge more
> closely: you can easily test for this bug by renaming your .sup directory away
> and creating a fresh sup directory.
Hello,
Has anyone been able to reproduce this bug on the relevant commit?
Edward
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-09-09 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 3:28 Edward Z. Yang
2010-07-31 9:00 ` Philipp Überbacher
2010-07-31 11:25 ` Ben Walton
2010-08-01 2:06 ` Edward Z. Yang
2010-08-01 2:15 ` Ben Walton
2010-08-15 23:58 ` Edward Z. Yang
2010-09-09 16:56 ` Edward Z. Yang [this message]
2010-10-29 0:31 ` Tero Tilus
2010-10-29 23:00 ` Tero Tilus
2010-10-29 23:29 ` Edward Z. Yang
2010-10-29 23:49 ` Matias Aguirre
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=1284051347-sup-9359@ezyang \
--to=ezyang@mit.edu \
--cc=bwalton@artsci.utoronto.ca \
--cc=sup-talk@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