Displaying 3 results from an estimated 3 matches for "keepclassx".
Did you mean:
keepclass
2018 Jan 24
2
Why R should never move to git
On 24/01/2018 6:35 PM, G?bor Cs?rdi wrote:
> When you create a branch for your bug fix, don't create it off the
> previous fix. Create it off the original, forked state of the repo.
Branches keepclass2 through to keepclass5 are my attempts to do that.
As far as I can see they are all the same as keepclass, which was
branched from the head of the master branch of my fork.
>
>
2018 Jan 25
0
Why R should never move to git
You need to create a branch from the original master, if you do
git log master
then you'll see which commit that is: f735449d679686867e7d3ab70810b09e8cea6366
So create that branch off that and switch to the new branch:
git branch keepclassx f735449d679686867e7d3ab70810b09e8cea6366
git checkout keepclassx
Then do
git log keepclass
to see the id of the new commit that you want to put on top of the new
branch: 0307ccfaa799c5257258eda89f2526347099f0d0
and cherry-pick that:
git cherry-pick 0307ccfaa799c5257258eda89f2526347099f0d0
Now you...
2018 Jan 25
2
Why R should never move to git
.../2018 7:04 PM, G?bor Cs?rdi wrote:
> You need to create a branch from the original master, if you do
> git log master
> then you'll see which commit that is: f735449d679686867e7d3ab70810b09e8cea6366
>
> So create that branch off that and switch to the new branch:
> git branch keepclassx f735449d679686867e7d3ab70810b09e8cea6366
> git checkout keepclassx
>
> Then do
> git log keepclass
> to see the id of the new commit that you want to put on top of the new
> branch: 0307ccfaa799c5257258eda89f2526347099f0d0
> and cherry-pick that:
> git cherry-pick 0307ccfaa...