From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: some easy issues for those who want to get involved
Date: Tue, 05 Nov 2013 09:10:54 +0100 [thread overview]
Message-ID: <1383638882-sup-7342@qwerzila> (raw)
hi there,
there are a few easy issues in the issue-tracker [0] for those who want
to get involved in developing sup. Please check them out:
- #174: add a keybinding for opening a decoded attachment [1]
- #175: expunge script for maildir-syncback [2]
rewards:
- a better sup
- you get to be added to the contributors team for sup (on github) (yey!)
Cheers, Gaute
[0] https://github.com/sup-heliotrope/sup/issues?state=open
[1] https://github.com/sup-heliotrope/sup/issues/174
[2] https://github.com/sup-heliotrope/sup/issues/175
reply other threads:[~2013-11-05 8:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1383638882-sup-7342@qwerzila \
--to=eg@gaute.vetsj.com \
--cc=sup-devel@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