Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: Ben Walton <bwalton@artsci.utoronto.ca>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Behavior for sent messages
Date: Sat, 31 Jul 2010 22:06:34 -0400	[thread overview]
Message-ID: <1280628309-sup-7092@ezyang> (raw)
In-Reply-To: <1280575476-sup-2567@pinkfloyd.chass.utoronto.ca>

Excerpts from Ben Walton's message of Sat Jul 31 07:25:38 -0400 2010:
> I'm running pretty close to the tip of git/next and that's not the
> behaviour here.  There are times, when using Maildir that the sent
> message doesn't get added immediately, but it always pops up at the
> next poll.

Hello Ben,

I tested your hypothesis and noted that the messages did not pop up
with a poll.

Since this behavior does not seem intentional, I guess it's a regression
caused by some combination of factors (possibly the new backsync branch?)
I'll try to reproduce on a clean Maildir with sup commit 900768918490a1040b55e2216f7f5429b2dadf84

Cheers,
Edward
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-08-01  2:09 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 [this message]
2010-08-01  2:15     ` Ben Walton
2010-08-15 23:58       ` Edward Z. Yang
2010-09-09 16:56         ` Edward Z. Yang
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=1280628309-sup-7092@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