From: "rara7020 ." <matthieu.rakotojaona@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Security advisory, releases 0.13.2.1 and 0.14.1.1
Date: Wed, 30 Oct 2013 14:51:03 +0100 [thread overview]
Message-ID: <CAMiZLn32Eg9G4Mt=_qZ4m_r0hctx-+HxdJvhKFuatytZ7iqWGg@mail.gmail.com> (raw)
In-Reply-To: <1383122092-sup-2694@qwerzila>
Hello,
Nice catch. Thank you for your management of this issue.
--
Matthieu RAKOTOJAONA
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2013-10-30 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 10:54 Gaute Hope
2013-10-30 8:38 ` Gaute Hope
2013-10-30 13:51 ` rara7020 . [this message]
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='CAMiZLn32Eg9G4Mt=_qZ4m_r0hctx-+HxdJvhKFuatytZ7iqWGg@mail.gmail.com' \
--to=matthieu.rakotojaona@gmail.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