From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 43400-done@debbugs.gnu.org
Subject: bug#43400: [PATCH 00/12] Move some BioConductor to (gnu packages bioconductor)
Date: Mon, 14 Sep 2020 21:42:14 +0200 [thread overview]
Message-ID: <87d02oxi09.fsf@elephly.net> (raw)
In-Reply-To: <20200914160414.7572-1-zimon.toutoune@gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> More janitoral stuff. The process is the same as described in the cover
> letter of #43345 <http://issues.guix.gnu.org/issue/43345>.
Thank you. I applied them all and added a commit to move a CRAN package
to (gnu packages bioconductor) because r-preprocesscore had been moved.
Pushed to “master” branch with commit 3159fcf145.
--
Ricardo
prev parent reply other threads:[~2020-09-14 19:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 16:04 [bug#43400] [PATCH 00/12] Move some BioConductor to (gnu packages bioconductor) zimoun
2020-09-14 16:07 ` [bug#43400] [PATCH 01/12] gnu: r-fourcseq: Move " zimoun
2020-09-14 16:07 ` [bug#43400] [PATCH 02/12] gnu: r-preprocesscore: " zimoun
2020-09-14 16:07 ` [bug#43400] [PATCH 03/12] gnu: r-rgraphviz: " zimoun
2020-09-14 16:07 ` [bug#43400] [PATCH 04/12] gnu: r-delayedmatrixstats: " zimoun
2020-09-14 16:07 ` [bug#43400] [PATCH 05/12] gnu: r-scran: " zimoun
2020-09-14 16:07 ` [bug#43400] [PATCH 06/12] gnu: r-scater: " zimoun
2020-09-14 16:07 ` [bug#43400] [PATCH 07/12] gnu: r-singlecellexperiment: " zimoun
2020-09-14 16:07 ` [bug#43400] [PATCH 08/12] gnu: r-beachmat: " zimoun
2020-09-14 16:07 ` [bug#43400] [PATCH 09/12] gnu: r-rhdf5lib: " zimoun
2020-09-14 16:07 ` [bug#43400] [PATCH 11/12] gnu: r-hitc: " zimoun
2020-09-14 16:07 ` [bug#43400] [PATCH 12/12] gnu: r-fithic: " zimoun
2020-09-14 16:07 ` [bug#43400] [PATCH 10/12] gnu: r-hdf5array: " zimoun
2020-09-14 19:42 ` Ricardo Wurmus [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d02oxi09.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=43400-done@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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://git.savannah.gnu.org/cgit/guix.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).