From: Benda Xu <heroxbd@gmail.com>
To: gentoo-soc@lists.gentoo.org
Cc: Denis Dupeyron <calchan@gentoo.org>
Subject: Re: [gentoo-soc] R_Overlay: Automated overlay maintenance - progress report #12
Date: Wed, 25 Sep 2013 11:11:40 +0900 [thread overview]
Message-ID: <CAMWv3tFVz1_eca2J62ZZHMv2SDv-4h3a+mrs6eXk32dkMnx3gA@mail.gmail.com> (raw)
In-Reply-To: <CAGrucu1h__Lpcc98KEouh-QxWenkr4Rf37K--EpUxgo3cksP7g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
Dear André,
Very impressive, I am a regular user of roverlay now.
Denis, I see bugs here and there, like the infamous
upstream-sliently-changes-tarball, I would like to apply to co-maintain the
roverlay if feasible. I am using R in my daily work, and I expect quick
fixes would benefit both myself and general users.
Cheers,
Benda
[-- Attachment #2: Type: text/html, Size: 417 bytes --]
prev parent reply other threads:[~2013-09-25 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 7:44 [gentoo-soc] R_Overlay: Automated overlay maintenance - progress report #12 André Erdmann
2013-09-25 2:11 ` Benda Xu [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=CAMWv3tFVz1_eca2J62ZZHMv2SDv-4h3a+mrs6eXk32dkMnx3gA@mail.gmail.com \
--to=heroxbd@gmail.com \
--cc=calchan@gentoo.org \
--cc=gentoo-soc@lists.gentoo.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