From csardi.gabor at gmail.com  Tue May 26 20:16:00 2015
From: csardi.gabor at gmail.com (=?UTF-8?B?R8OhYm9yIENzw6FyZGk=?=)
Date: Tue, 26 May 2015 14:16:00 -0400
Subject: [Rd] MetaCran website v1.0.0-alpha
In-Reply-To: <CADwqtCME7DfMozU1OmGXX4et7MfQXwgLqaFn_JeaWPyDQ_jtSg@mail.gmail.com>
References: <CABtg=Km1Vi1SHK=X2vGiUf+rDrm-05U4n0Gqdbk=rE5o-+xnxw@mail.gmail.com>
	<m2wpzyl371.fsf@krugs.de>
	<0A08CC22-72B9-4FB4-B6E8-50E885F0506A@r-project.org>
	<CABtg=KmPdieqPJP4nn-bGX+5LOJh1L3yAg+tS36UxXOMRhTn8g@mail.gmail.com>
	<CANROs4fC5ytjrgrOkABtouF-8aZ6pBL6u9vDCQey4_ezwSB+2A@mail.gmail.com>
	<CADwqtCNcCB1i_OON0F1Nv5SxEHdYY=o++XEwF0bgttA0p+Chzw@mail.gmail.com>
	<CABdHhvHT6Pc6a89GNTUpW26Y=E_n6mD1hNwX160Kcx638OY3nQ@mail.gmail.com>
	<CADwqtCMfGisC+g_M29Sx+H8mz30wnfUBAOqE_rBvueiNjhNPgA@mail.gmail.com>
	<CABtg=KkOODVm7WmSrm0cCos_gDXc6f4NYZYa_p5QpzDdiNhCvw@mail.gmail.com>
	<CADwqtCME7DfMozU1OmGXX4et7MfQXwgLqaFn_JeaWPyDQ_jtSg@mail.gmail.com>
Message-ID: <CABtg=K=_wimtHb6ha3OS0hk4-Uksw4r3gD1yK-enCRp2Bxp61g@mail.gmail.com>

On Tue, May 26, 2015 at 2:10 PM, Gabriel Becker <gmbecker at ucdavis.edu>
wrote:
[...]

>
> Well, sort of. I mean if the package is being actively developed not on
> github, forking your archive repo and developing a patch/etc against it
> won't necessarily be particularly effective, as there is no way to have the
> right starting point (state of trunk), right?
>

Well, then you can do 1) git rebase or 2) get the patch if the original
repo is not in git.

Yes, this is not ideal. I could remove that "Browse the source" completely,
that is an option, and remove the link from the version number as well.
There there will be no links to github.com/cran. Experienced users will
just type in the URL. That's fine with me, too.

Btw. how does this look for a warning: https://github.com/cran/crayon
This is the most red I could find.

G.

	[[alternative HTML version deleted]]



[Rd] MetaCran website v1.0.0-alpha
=?UTF-8?B?R8OhYm9yIENzw6FyZGk=?=