Jeff King writes:
> On Mon, Jan 22, 2018 at 10:22:21PM -0500, Aleksey Bykov wrote:
>
>> I am a code reviewer, I have a situation in GIT:
>>
>> - before: a.txt
>>
>> Then a developer decided to split the content of a.txt into 2 files
>> and add a few changes all in one commit:
>>
>> - after: b.
On Mon, Jan 22, 2018 at 10:22:21PM -0500, Aleksey Bykov wrote:
> I am a code reviewer, I have a situation in GIT:
>
> - before: a.txt
>
> Then a developer decided to split the content of a.txt into 2 files
> and add a few changes all in one commit:
>
> - after: b.txt + few changes and c.txt + f
On Mon, Jan 22, 2018 at 7:22 PM, Aleksey Bykov wrote:
> Is there an easy way to see:
>
> 1. what came to b from a?
> 2 .what came to c from a?
> 3. all extra changes apart from just moving stuff?
One way to do this is to use "--color-moved" - it will tell you what
in b.txt and c.txt was moved and
Hello,
My problem:
I am a code reviewer, I have a situation in GIT:
- before: a.txt
Then a developer decided to split the content of a.txt into 2 files
and add a few changes all in one commit:
- after: b.txt + few changes and c.txt + few changes
Is there an easy way to see:
1. what came to b
4 matches
Mail list logo