Re: [PATCH 6/7] update git-stage.po

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH 6/7] update git-stage.po

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:51:14

Jonathan Nieder [off-list ref] writes:
Another thought I have had occasionally is that it would be nice if
the versions committed did not have line numbers while the working
copy had line numbers, so an ordinary 3-way merge could be more likely
to work for integrating changes[1].  But this second thought is less
fully cooked. :)
I would rather see that done as a customized content-level merge backend,
i.e. at the same level as binary and union merges are specified. Losing
line number information just for the sake of the generic merge that does
not have domain knowledge (read: "stupid") is a way suboptimal solution to
the problem, I would think.

Re: [PATCH 6/7] update git-stage.po

From: Jonathan Nieder <hidden>
Date: 2016-06-15 22:51:14

Junio C Hamano wrote:
I would rather see that done as a customized content-level merge backend,
i.e. at the same level as binary and union merges are specified. Losing
line number information just for the sake of the generic merge that does
not have domain knowledge (read: "stupid") is a way suboptimal solution to
the problem, I would think.
Oh!  You are definitely right.  Thank you.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help