Closed lcolladotor closed 7 years ago
Thanks @sampoll!
I guess that the next step is to git cherry-pick
commits https://github.com/rafalab/bumphunter/commit/718d3d87af114f8dc404c3889c673fac861bb84c through https://github.com/rafalab/bumphunter/commit/8ae30a7daddec1b7e70d789cebb43f195a537a35 to Bioconductor. Then https://github.com/Bioconductor-mirror/bumphunter/commits/master would be updated.
In your local clone of rafalab/bumphunter, you'll have to run the update_remotes.sh
script (see http://www.bioconductor.org/developers/how-to/git-mirrors/ for details). That will create a devel
branch locally.
Basically, from scratch it would be something like this (assuming you have git-svn
installed):
git clone https://github.com/rafalab/bumphunter.git
curl -O https://raw.githubusercontent.com/Bioconductor/mirror/master/update_remotes.sh
cd bumphunter
bash ../update_remotes.sh
## See all the branches
git branch
git checkout devel
git cherry-pick 718d3d..8ae30a7
## You'll need svn write permissions for the bumphunter package to do this (and a svn passwd).
## Rafa can request Bioc to give them to you. I believe that you'll need to add yourself
## to the DESCRIPTION file as a maintainer. Talk about this with Rafa.
git svn dcommit
## After a couple of seconds you can update your local clone
git pull
## And return to the master branch
git checkout master
The git cherry-pick
step might be a bit more complicated than what I posted.
Best, Leo
I'm working on it. I need to be sure I know what I'm doing, because I definitely don't want to mangle Bioconductor's subversion repository. I think that would make me very unpopular with Bioconductor.
On 5/10/17 9:51 AM, Leonardo Collado-Torres wrote:
Thanks @sampoll https://github.com/sampoll!
I guess that the next step is to |git cherry-pick| commits rafalab/bumphunter@718d3d8 https://github.com/rafalab/bumphunter/commit/718d3d87af114f8dc404c3889c673fac861bb84c through rafalab/bumphunter@8ae30a7 https://github.com/rafalab/bumphunter/commit/8ae30a7daddec1b7e70d789cebb43f195a537a35 to Bioconductor. Then https://github.com/Bioconductor-mirror/bumphunter/commits/master would be updated.
In your local clone of rafalab/bumphunter, you'll have to run the |update_remotes.sh| script (see http://www.bioconductor.org/developers/how-to/git-mirrors/ for details). That will create a |devel| branch locally. Basically, from scratch it would be something like this (assuming you have |git-svn| installed):
|git clone https://github.com/rafalab/bumphunter.git curl -O https://raw.githubusercontent.com/Bioconductor/mirror/master/update_remotes.sh cd bumphunter bash ../update_remotes.sh ## See all the branches git branch git checkout devel git cherry-pick 718d3d..8ae30a7 ## You'll need svn write permissions for the bumphunter package to do this (and a svn passwd). ## Rafa can request Bioc to give them to you. I believe that you'll need to add yourself ## to the DESCRIPTION file as a maintainer. Talk about this with Rafa. git svn dcommit ## After a couple of seconds you can update your local clone git pull ## And return to the master branch git checkout master |
The |git cherry-pick| step might be a bit more complicated than what I posted.
Best, Leo
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rafalab/bumphunter/pull/17#issuecomment-300488232, or mute the thread https://github.com/notifications/unsubscribe-auth/AZaxcgevhiVhtrOJ5BHkkUwYLvbZ-R3Bks5r4cDmgaJpZM4NV5m9.
This commit resolves https://github.com/rafalab/bumphunter/issues/15 by adding the arguments
mappingInfo
andsimplifyGeneID
toannotateTranscripts()
.mappingInfo
is a named list whose elements are passed toAnnotateDbi::mapIds()
for more flexible gene id matching between a given TxDb object and the organism package (like org.Hs.eg.db).simplifyGeneId
is a logical and if TRUE gene ids likeENSTsomething.8_etc
get simplified toENSTsomething
. This allows working with TxDb objects created from GENCODE GTF files and matching then to org.Hs.eg.db as if the ids were ENSEMBL gene ids.A unit test checking the new changes has been added as well.
A check and build reveals no new notes/warnings/errors.