From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add Ribotaper.
Date: Sat, 9 Jul 2016 21:43:44 +0200 [thread overview]
Message-ID: <87mvlq38cv.fsf@elephly.net> (raw)
In-Reply-To: <57802E95.1020305@uq.edu.au>
Ben Woodcroft <b.woodcroft@uq.edu.au> writes:
>> I think in the ribotaper/bedtools case we should just name the variable
>> “bedtools-2.18” and make it public.
>
> I agree with should call it 'bedtools-2.18' and make it public (but with
> a comment explaining why the old version is kept), just as in e.g.
> 'python-flake8-2.2.4'.
>
> Are you suggesting we keep bedtools-2.18 even if ribotaper updates to a
> newer version? I thought accepted practice was to delete old packages
> when they are no longer needed.
No, I agree. We keep bedtools-2.18 as long as it’s needed for
Ribotaper.
> The patch LGTM otherwise, except that I would unpack 'ORF' and use the
> term 'ribo-seq' in the description. I've never looking at ribo-seq data
> before and I'm not familiar, so I wasn't sure what 'ribosome profiling'
> meant exactly e.g. is it measuring the amount of ribosome in a cell? I
> realise that isn't true, just illustrating the point. Perhaps I am too
> naive.
I don’t know how to naturally include the term “ribo-seq”, so how about
simply this:
Ribotaper is a method for defining translated @dfn{open reading
frames} (ORFs) using ribosome profiling (ribo-seq) data. This
package provides the Ribotaper pipeline.
Is this better?
~~ Ricardo
next prev parent reply other threads:[~2016-07-09 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 9:26 [PATCH] Add Ribotaper Ricardo Wurmus
2016-07-07 9:26 ` [PATCH] gnu: " Ricardo Wurmus
2016-07-07 13:32 ` [PATCH] " Ben Woodcroft
2016-07-07 13:45 ` Ricardo Wurmus
2016-07-08 22:52 ` Ben Woodcroft
2016-07-09 19:43 ` Ricardo Wurmus [this message]
2016-07-10 11:30 ` Ben Woodcroft
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=87mvlq38cv.fsf@elephly.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=b.woodcroft@uq.edu.au \
--cc=guix-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.