Re: [PATCHv5 17/17] diff.c: color moved lines differently
- From
Stefan Beller <sbeller@google.com>
- Date
- May 25, 2017, 05:39 UTC
- Message-ID
- <CAGZ79kZBOoK2vd5EqottnUr1AYMHa1=TzQB8ga00TehQxgtuhA@mail.gmail.com>
- In-Reply-To
- <xmqqk255fz7b.fsf@gitster.mtv.corp.google.com>
On Wed, May 24, 2017 at 7:27 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 20 quoted lines
> Stefan Beller <sbeller@google.com> writes: > >> When a patch consists mostly of moving blocks of code around, it can >> be quite tedious to ensure that the blocks are moved verbatim, and not >> ... >> cases. This leads to another thought: We could pass on '--color-moved' to >> submodules such that they color up moved lines for themselves. If we'd do >> so only line moves within a repository boundary are marked up. >> >> Helped-by: Jonathan Tan <jonathantanmy@google.com> >> Signed-off-by: Stefan Beller <sbeller@google.com> >> Signed-off-by: Junio C Hamano <gitster@pobox.com> >> >> # Conflicts: >> # diff.c >> Signed-off-by: Junio C Hamano <gitster@pobox.com> >> Signed-off-by: Stefan Beller <sbeller@google.com> >> --- > > Hmph, what are these final lines about?
See the explanation in the patch 16/17. My guess is that one of us (me) was careless again.
The commented lines are easily produced by git-gui, that I use. I think it just takes the commit message from the underlying git-core. But unlike git-core, it doesn't strip off commented lines as there is no extra information in comments presented. I wonder how you are the first signoff after the conflict markers though, as that would hint that you signed off a commit message with the commented conflict lines first, before I had them.
Puzzeled, will fix in a reroll.
Thanks, Stefan