[Rd] Why R should never move to git
csardi.gabor at gmail.com
Thu Jan 25 01:52:54 CET 2018
On Thu, Jan 25, 2018 at 12:43 AM, Duncan Murdoch
<murdoch.duncan at gmail.com> wrote:
> But that's only half the battle. If I did that and emailed the diff to a
> maintainer, I'm guessing I'd be told I should put together a PR instead.
> And as I found out, that's not easy, if I already have a fork of the
> repository that contains changes and I don't want to blow it away.
You can always create a branch, off any commit in the DAG, as in the
and then replay the changes there.
But there are alternatives as well, e.g. you can also create a branch
from the tip of master,
and then remove the two old commits, and keep the last one. I usually
do this via sg like
git rebase HEAD^^^^ --interactive
which will start an editor with the 4 latest commits. Then you just
remove the ones
you don't want, save, exit, and then git will perform the rebase, as desired.
> Duncan Murdoch
More information about the R-devel