Kyle,
Assuming the fix you want to apply to the release branch is
https://github.com/kbemis/Cardinal/commit/93ca48aa105379e4b052b094690ba927d6ab6a6a
You can use this procedure.
git clone https://github.com/kbemis/Cardinalcd Cardinal
curl -O
https://raw.githubusercontent.com/Bioconductor/mirror/m
Kyle,
You will need to provide more details, particularly what Bioconductor
package you are trying to update and where the existing GitHub repository
is located.
The “Unable to determine SVN information from working tree history” errors
suggest the remotes were not setup properly for the reposito
Hi Kyle,
What I've done in your situation is to simply svn checkout the release
branch. Then copy the latest files from my local release code into it,
then use svn to push it to the Bioc-release trunk.
Here's an example using my `derfinder` package:
```bash
## Work somewhere where the 'derfinder
Oops, those newly added functions in GenomicFeatures are
GenomicFeatures::mapRangesToIds
GenomicFeatures::mapIdsToRanges
Martin
From: Bioc-devel [bioc-devel-boun...@r-project.org] on behalf of Morgan, Martin
[martin.mor...@roswellpark.org]
Sent: Friday, D
Dear all,
I’m working from a prior-existing Github repo, and trying to commit a bug fix
to the release-3.2 branch, and git svn is only giving me errors.
Trying 'git svn info' or 'git svn rebase’ only gives me “Unable to determine
SVN information from working tree history”
The potential fixes I
Hi Ludwig --
It would be really great to see what you've put together; can you make your
code available somewhere, maybe via github?
I think the facilities already in Bioconductor include:
- select() and the OrganismDb (e.g., Homo.sapiens) packages
- (Recently introduced, in bioc-devel) Genomi
Ok. Could it at least issue a warning when some seqlevels are not mappable?
Thanks,
Michael
On Thu, Dec 17, 2015 at 3:40 PM, Hervé Pagès wrote:
> Hi Michael,
>
> On 12/17/2015 02:45 PM, Michael Lawrence wrote:
>>
>> Seems like seqlevelsStyle<- between e.g. UCSC and NCBI does not work
>> outside
