sleepy_penguin RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Joan Touzet <joant@atypical.net>
To: sleepy.penguin@librelist.org
Subject: Re: [sleepy.penguin] [ANN] sleepy_penguin 3.3.0 - fixes and compatibility improvements
Date: Wed, 1 Jan 2014 15:27:56 -0500 (EST)	[thread overview]
Message-ID: <19600297.397.1388608073456.JavaMail.Joan@RITA> (raw)
In-Reply-To: 19600297.397.1388608073456.JavaMail.Joan@RITA

unsubscribe


       reply	other threads:[~2014-01-01 20:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01 20:27 Joan Touzet [this message]
2014-01-01 21:28 ` [sleepy.penguin] [ANN] sleepy_penguin 3.3.0 - fixes and compatibility improvements Eric Wong
  -- strict thread matches above, loose matches on Subject: below --
2013-12-30  1:34 Eric Wong

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

  List information: https://yhbt.net/sleepy_penguin/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19600297.397.1388608073456.JavaMail.Joan@RITA \
    --to=joant@atypical.net \
    --cc=sleepy.penguin@librelist.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.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/sleepy_penguin.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).