search for: unforked

> On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > > R-Forge is mirrored on Github; see https://github.com/rforge/ecdat, for example. That shows 418 commits in its history; presumably that's the full R-forge history. I think that's newer than Michael Friendly's gist. > > So I suspect (but haven't tried to do this) that

????? Thanks to Duncan, Lionel and Henrik for their quick replies. I have further questions: ??? ?? ???? 1.? Will GitHub automatically transfer the commits I made to R-Forge in the past couple of days?? R-Forge is now at Rev. 420, and GitHub is still at 418.? Will 419 and 420 be automatically mirrored onto "https://github.com/rforge/ecdat" sometime in the next 24 hours or so?? Is

Whereas it is true that one has to contact GitHub to detach a GitHub repository, it really is no problem (or at least was no problem in 2016). I wanted to do so when I took over the maintainer role of LaplacesDemon which only remained on GitHub as a fork on some other person's private account. So I forked and then contacted GitHub support and simply asked them to remove the "forked

...project maintainer wants things to work, you?re probably stuffed. Quite frankly, your opinion doesn?t matter as much as that of the person who designed the system and has been maintaining it for the last N years. As long as that person holds well-regarded opinions, his project is likely to remain unforked, and your contribution will remain disregarded. I can summarize all of the above with, ?It?s difficult to work with other people,? but that?s no particular failing of open source software. That?s just people.

????? Thanks.? I'm still having problems: ??? ??????? 1.? I went to "github.com" and logged in with my standard GitHub account ??? ??????? 2.? Then I clicked "+" in the upper right, just left of my GitHub ID icon, and selected "Import a repository", as Lionel suggested. ??? ??????? 3.? " Your old repository?s clone URL" =

I think all 3 issues are solved by: 1. Use the "+" button on github.com <http://github.com/> and select "Import a repository". 2. Pass the URL of your SVN repo. Lionel > On 26 Jun 2019, at 18:58, Spencer Graves <spencer.graves at prodsyse.com> wrote: > > Thanks to Duncan, Lionel and Henrik for their quick replies. I have further questions: >

Re your point 3: Because you have managed to create a GitHub version of your repository that is not a fork of https://github.com/rforge/ecdat, but its own independent repository, contacting GitHub support might not be the right way forward. Note that https://github.com/rforge is simply a read-only mirror of the complete R-Forge repository (and at least to me it is unclear of whether GitHub itself

Hi, Henrik Singmann et al.: ????? Thanks for the suggestions.? I tried again to pull "https://github.com/sbgraves237/Ecdat" from R-Forge, with the same "Error 500" as before.? Then I tried pulling from "https://github.com/rforge/ecdat", which seemed to work ... AND the copy I pulled was at the latest revisions I had posted to R-Forge (520), so that makes it

On 26/06/2019 1:38 p.m., Spencer Graves wrote: > ????? Thanks.? I'm still having problems: > > > ??? ??????? 1.? I went to "github.com" and logged in with my standard > GitHub account > > > ??? ??????? 2.? Then I clicked "+" in the upper right, just left of my > GitHub ID icon, and selected "Import a repository", as Lionel

Hello, All: ????? What's the status and future plans for R-Forge? ????? I ask primarily because a problem I reported May 15 and 17 via two different channels has yet to be fixed, and it prevents my development versions of the Ecdat and Ecfun packages from building -- because the Windows version cannot find "Matrix";? see below. Secondarily, the version of R that R-Forge

Henrik's advice is all good. I would say his idea of the final commit of a README pointer is better than deleting things at R-forge; there is likely old information out there somewhere pointing to R-forge as a location for Ecdat development, and any bug reports or discussion on R-forge will not have been copied over to Github. Duncan Murdoch On 28/06/2019 4:14 a.m., Henrik Singmann

On Fri, Jul 28, 2017 at 06:13:42PM +0200, hw wrote: > What?s the point of doing this with Fedora? It?s not like bugs > were fixed before Fedora is EOL and all reports are forgotten. Many bugs are fixed in Fedora. Many more bugs are fixed in the upstreams. Please remember that Fedora is primarily an *integration* project, and the best way to get bugs fixed is for the developers of the code