Perfect. Many thanks!
 - Alex

> On Apr 24, 2018, at 8:25 AM, Turaga, Nitesh <nitesh.tur...@roswellpark.org> 
> wrote:
> 
> Ok, please check if everything on the master branch is as expected. I’ve 
> synced it.
> 
> Best
> 
> Nitesh 
>> On Apr 24, 2018, at 11:20 AM, Alexander Pico <alex.p...@gladstone.ucsf.edu> 
>> wrote:
>> 
>> It’s ready. Thanks!
>> 
>> - Alex
>> 
>>> On Apr 24, 2018, at 8:02 AM, Turaga, Nitesh <nitesh.tur...@roswellpark.org> 
>>> wrote:
>>> 
>>> Hi 
>>> 
>>> Go ahead and clean your repo. 
>>> 
>>> Once that is done, I can sync it.
>>> 
>>> Best,
>>> 
>>> Nitesh 
>>> 
>>>> On Apr 22, 2018, at 9:07 PM, Alex Pico <alex.p...@gladstone.ucsf.edu> 
>>>> wrote:
>>>> 
>>>> In an effort to clear a BiocCheck warning and reduce the size of our code 
>>>> base from 22MB to 7MB, I’d like to sync our recently cleaned git objects 
>>>> (using the same BFG tool as described below). I understand that I, as a 
>>>> maintainer, can not push these sorts of changes to the Bioconductor 
>>>> server. Can someone help with this sync?
>>>> 
>>>> https://github.com/cytoscape/RCy3
>>>> git.bioconductor.org:packages/RCy3.git
>>>> 
>>>> Thanks!
>>>> - Alex
>>>> 
>>>>> On Mar 19, 2018, at 11:29 AM, Turaga, Nitesh 
>>>>> <nitesh.tur...@roswellpark.org> wrote:
>>>>> 
>>>>> Another note, it is not be possible for you to push back to the 
>>>>> Bioconductor server once the repo is cleaned. Please do this on your 
>>>>> Github repo, and let me know. I will sync the cleaned repo.
>>>>> 
>>>>> To further explain, you need force push privileges to Bioconductor to 
>>>>> make this happen, and these are not given to maintainers. Hence the added 
>>>>> step required for me to sync these repos.
>>>>> 
>>>>> I’m also forwarding to Bioc-devel, since this is a particularly good 
>>>>> question to share with the community at large. We’ve been getting a few 
>>>>> questions pertaining this exact problem.
>>>>> 
>>>>> Best
>>>>> 
>>>>>> On Mar 19, 2018, at 2:24 PM, ni41435_ca <nitesh.tur...@roswellpark.org> 
>>>>>> wrote:
>>>>>> 
>>>>>> Hi Vincent,
>>>>>> 
>>>>>> Yes it is possible to prune this. Please check BFG cleaner, it works 
>>>>>> well.
>>>>>> 
>>>>>> https://rtyley.github.io/bfg-repo-cleaner/
>>>>>> 
>>>>>> That would be the easiest way to go about it. If you need more help, 
>>>>>> please feel free to ask. BFG cleaner is pretty well explained in its 
>>>>>> documentation.
>>>>>> 
>>>>>> Best,
>>>>>> 
>>>>>> Nitesh 
>>>>>> 
>>>>>>> On Mar 19, 2018, at 2:22 PM, Vincent Carey <st...@channing.harvard.edu> 
>>>>>>> wrote:
>>>>>>> 
>>>>>>> Hi -- restfulSE is hard to check out the first time because
>>>>>>> so many large objects were in there, and then deleted.
>>>>>>> 
>>>>>>> Is it allowable to prune them out?  If so can you advise
>>>>>>> on the commands?
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> This email message may contain legally privileged and/or confidential 
>>>>> information.  If you are not the intended recipient(s), or the employee 
>>>>> or agent responsible for the delivery of this message to the intended 
>>>>> recipient(s), you are hereby notified that any disclosure, copying, 
>>>>> distribution, or use of this email message is prohibited.  If you have 
>>>>> received this message in error, please notify the sender immediately by 
>>>>> e-mail and delete this email message from your computer. Thank you.
>>>>> _______________________________________________
>>>>> Bioc-devel@r-project.org mailing list
>>>>> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>>>> 
>>> 
>>> 
>>> 
>>> This email message may contain legally privileged and/or confidential 
>>> information.  If you are not the intended recipient(s), or the employee or 
>>> agent responsible for the delivery of this message to the intended 
>>> recipient(s), you are hereby notified that any disclosure, copying, 
>>> distribution, or use of this email message is prohibited.  If you have 
>>> received this message in error, please notify the sender immediately by 
>>> e-mail and delete this email message from your computer. Thank you.
> 
> 
> 
> This email message may contain legally privileged and/or confidential 
> information.  If you are not the intended recipient(s), or the employee or 
> agent responsible for the delivery of this message to the intended 
> recipient(s), you are hereby notified that any disclosure, copying, 
> distribution, or use of this email message is prohibited.  If you have 
> received this message in error, please notify the sender immediately by 
> e-mail and delete this email message from your computer. Thank you.

_______________________________________________
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel

Reply via email to