Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: Felix Glaser <felix.glaser@rwth-aachen.de>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sent mails don't show up
Date: Sat, 30 Apr 2011 08:12:50 -0400	[thread overview]
Message-ID: <1304165533-sup-1163@ezyang> (raw)
In-Reply-To: <1304159425-sup-173@alpha>

Known bug, I've been meaning to investigate and fix but haven't
gotten 'round to it.  You can find the email you've just sent by
searching label:sent, and if you press 'a' it will be unarchived.

Edward

Excerpts from Felix Glaser's message of Sat Apr 30 06:32:40 -0400 2011:
> Hi *,
> 
> after upgrading to sup 0.12.1, sent mails are not shown in sup anymore until a
> reply reaches me, is that the indented behavior? and how can I change that?
> 
> cheers leex
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


      reply	other threads:[~2011-04-30 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-30 10:32 Felix Glaser
2011-04-30 12:12 ` Edward Z. Yang [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=1304165533-sup-1163@ezyang \
    --to=ezyang@mit.edu \
    --cc=felix.glaser@rwth-aachen.de \
    --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