[R-pkg-devel] Advice on R-forge to Github migration
jdnewm|| @end|ng |rom dcn@d@v|@@c@@u@
Sun Jan 31 19:35:56 CET 2021
Technically, git does not record file history... it records commit history, and reconstructs file history as needed. The contents of a file identify it uniquely among all commits ever made regardless of which directory it was ever in. IMO this is the main reason why git is superior and I put up wth the inconsistent command line interface because of it.
git mv is very simple .
On January 31, 2021 10:21:09 AM PST, Joshua Ulrich <josh.m.ulrich using gmail.com> wrote:
>On Sun, Jan 31, 2021 at 12:10 PM Duncan Murdoch
><murdoch.duncan using gmail.com> wrote:
>> rgl has been on R-forge for a long time, but I am now planning on
>> migrating it to Github. I really dislike git, but Github offers
>> benefits, and nowadays I'm familiar enough with them, that I think
>> be better off there.
>> The easiest way to do this would be to do almost nothing: just
>> the the dmurdoch/rgl fork of r-forge/rgl is now where all new changes
>> will be committed.
>> Can anyone else who has done this migration tell me if there there
>> disadvantages to this that I don't know about? What I know:
>> - I'll lose the bug reports and forum discussions that were sent to
>> - I'll need to do a bit of work to change dmurdoch/rgl to a more
>> standard R package layout, but this should be quite easy: basically
>> just moving the files in pkg/rgl to the top level. I assume "git mv"
>> will keep their history if I do this.
>I've moved history and issues from R-Forge to GitHub for half a dozen
>R packages. I might be able to do this rgl. At minimum, I could help
>you do it.
>Yes, git mv will retain the file history.
>> Duncan Murdoch
>> R-package-devel using r-project.org mailing list
Sent from my phone. Please excuse my brevity.
More information about the R-package-devel