From: Eric Weikl <eric.weikl@gmx.net>
To: Gaute Hope <eg@gaute.vetsj.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Getting ready for sup-0.13
Date: Sun, 28 Apr 2013 21:59:56 +0200 [thread overview]
Message-ID: <1367178536-sup-1766@mint> (raw)
In-Reply-To: <517D7208.2040907@gaute.vetsj.com>
Hi Gaute,
thanks to you guys for giving some focus - I'm very happy that sup
development is gaining some traction again!
Excerpts from Gaute Hope's message of 2013-04-28 21:01:28 +0200:
> @ericweikl: you already did some work to keep the maildir branch up to
> date so if you wish you could add yourself to the maildir-sync branch
> responsible at the same wikipage.
Sure, I definitely want to finish what I started :-) I just added myself.
Cheers,
Eric
next prev parent reply other threads:[~2013-04-28 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 18:23 Gaute Hope
2013-04-28 18:47 ` [sup-talk] " Jonathan Lassoff
2013-04-28 19:01 ` Gaute Hope
2013-04-28 19:59 ` Eric Weikl [this message]
2013-04-28 19:05 ` Steven Hum
2013-04-28 20:33 ` Ico Doornekamp
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=1367178536-sup-1766@mint \
--to=eric.weikl@gmx.net \
--cc=eg@gaute.vetsj.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