From: Steven Hum <sdothum@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Who needs Heliotrope when you've got backwards label synchronization
Date: Sat, 01 Dec 2012 19:00:50 -0500 [thread overview]
Message-ID: <1354406275-sup-6416@luna> (raw)
In-Reply-To: <1354404870-sup-6839@javelin>
Thank you, Edward! I certainly was not expecting this, so soon!
I am going to check out your new patchset immediately!
Steven
Excerpts from Edward Z. Yang's message of 2012-12-01 18:35:44 -0500:
> I've finally cleaned up and "released" the patchset that I
> use on a regular basis on top of Sup. It is described here:
>
> http://blog.ezyang.com/2012/12/maildir-synchronizing-sup/
>
> Cheers,
> Edward
--
"Truth or die."
Steven Hum
5 - 28 Gilmour St
Ottawa, ON K2P 0N3
email sdothum@gmail.com
tel 613.237.9058
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2012-12-02 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-01 23:35 Edward Z. Yang
2012-12-02 0:00 ` Steven Hum [this message]
2012-12-02 0:03 ` 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=1354406275-sup-6416@luna \
--to=sdothum@gmail.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