Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: William Baxter <web-sup@superscript.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Simple E-Mail Delaying
Date: Sun, 04 Oct 2009 11:51:51 -0400	[thread overview]
Message-ID: <1254671303-sup-2911@kronos> (raw)
In-Reply-To: <1254659599-sup-7377@peray>

Excerpts from Nicolas Pouillard's message of Sun Oct 04 08:36:02 -0400 2009:
> I've written a blog post about improving my email experience. And since it
> interacts nicely with sup it may be of some interest for you.

I also employ a tickler system in sup, one that relies exclusively on labels.
To mark a thread for review on day DD of the month, label it with #DD.
Obviously this extends forward only one month.  I have not found that
problematic.  I also use #E to indicate the need to reply, #W as waiting for
something, #A for action required, etc.

The choice of # came from two considerations.  First, it sorts before letters.
Second, it does not require quoting in searches.  The date labels could do
without the prefix, but I began with the #<letter> labels, and like the way
that the common prefix sets these elements apart in label-list-mode.

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


  parent reply	other threads:[~2009-10-04 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-04 12:36 Nicolas Pouillard
2009-10-04 14:46 ` Steve Goldman
2009-10-05  7:55   ` Nicolas Pouillard
2009-10-05 22:11     ` Nicolas Pouillard
2009-10-04 15:51 ` William Baxter [this message]
2009-10-05  7:59   ` Nicolas Pouillard

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=1254671303-sup-2911@kronos \
    --to=web-sup@superscript.com \
    --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