From murdoch.duncan at gmail.com  Thu Jan 25 01:43:41 2018
From: murdoch.duncan at gmail.com (Duncan Murdoch)
Date: Wed, 24 Jan 2018 19:43:41 -0500
Subject: [Rd] Why R should never move to git
In-Reply-To: <CABtg=Km0O67Xo_vEoqiS0ny27qzo4mJTtWSJOjO8OUatLFUk+A@mail.gmail.com>
References: <10a2b81e-4d5d-e387-5e0d-bfe58fbf16ca@gmail.com>
 <CABtg=K=apVWjEaE6pcv0FBkOMDJHFeBLPi9VU3n_+xmuYs4gVg@mail.gmail.com>
 <ba18a519-73c0-5b00-ae47-5b7e411e1600@gmail.com>
 <CABtg=KkzmuqeGmi2JUa5fOJXrY_9=J2Z7Uh3s68Y99GQACgUBw@mail.gmail.com>
 <e2b65210-ef35-9975-0aef-648ab81f289b@gmail.com>
 <CABtg=Km0O67Xo_vEoqiS0ny27qzo4mJTtWSJOjO8OUatLFUk+A@mail.gmail.com>
Message-ID: <f47a64d9-f7cc-b2e6-c153-38c6ee71a252@gmail.com>

On 24/01/2018 7:29 PM, G?bor Cs?rdi wrote:
> On Thu, Jan 25, 2018 at 12:24 AM, Duncan Murdoch
> <murdoch.duncan at gmail.com> wrote:
> [...]
>> Thanks, those instructions appear to have worked.
>>
>> For comparison purposes, the equivalent steps in svn would be
>>
>> svn diff -r PREV:HEAD --internal-diff > patchfile
>>
>> and then the patchfile could be sent to the maintainer.
> 
> If you just want the diff corresponding to the last commit,
> 
> git show
> 
> will print it for you. Or
> 
> git show keepclass
> 
> for a specific branch.

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.

Duncan Murdoch



[Rd] Why R should never move to git
Duncan Murdoch