git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/PATCH] mergetool: use resolved conflicts in all the views

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Dec 19, 2020, 00:53 UTC
Message-ID
<5fdd4f22c473b_1d952220844@natae.notmuch>
In-Reply-To
<20201219001358.GA153461@ellen>
Seth House wrote:
Show 13 quoted lines
> On Fri, Dec 18, 2020 at 03:46:37AM -0600, Felipe Contreras wrote:
> > Yes, but the author of diffconflicts is not infallible.
> > 
> > Explain why the *users* of the diffconclits tool would be affected
> > negatively
> 
> You've got that right -- I'm definitely not infallible. My point isn't
> that I'm right; my point is that is my *preference*. Other mergetool
> authors may have different preferences.
> 
> I think where we're not seeing eye-to-eye is that you're focusing on
> potential "negative" consequences whereas I'm talking about having more
> information about the merge rather than less.

Yes, but it's not due to some unreasonable hankering; it comes from a deep philosophical reason, which is Karl Popper's falsifiability principle [1] that solves both the problems of induction and demarcation.

To put it plainly; if we want to know if all swans are white, where you claim the negative, and I the positive; it's much easier for you to prove the negative. All you need is *one* black swan.

Analogously in our case; all you need is *one* negative consequence to prove your point, while me providing one hundred success cases does not prove my point.

> There is very likely no negative consequences for most, if not all,
> mergetools.
Again: do you have *one* negative consequence that is present in tool a,
but not in tool b?

You say there is "very likely no negative consequences", but do you have evidence of *any* negative consequence?

> I wrote the initial version of diffconflicts ten years ago and I've
> been using it nearly every day since. I'm fairly confident in the end
> result. What is a fact is there is undisputedly less information about
> the merge if we overwrite LOCAL and REMOTE;
But it's objectively not useful information.

Edit your make-conflicts.sh script, and remove the first paragraph from poem.txt.

What happens when you run "git merge"?
Does it not complete the merge without *any* user interaction?

Doesn't that mean that git considers the changes in the second paragraph to be non-conflicts?

> This is where I will part this particular debate.
All right.

I'm still waiting for anyone to provide *one* example of a negative consequence.

Cheers.
[1] https://en.wikipedia.org/wiki/Falsifiability
-- 
Felipe Contreras
Previous: Seth HouseNext: Junio C Hamano
Message 21 of 70 in “mergetool: use resolved conflicts in all the views”
  1. mergetool: use resolved conflicts in all the viewsFelipe Contreras, Dec 16, 2020
  2. Junio C HamanoDec 16, 2020
  3. Seth HouseDec 16, 2020
  4. Junio C HamanoDec 17, 2020
  5. Felipe ContrerasDec 17, 2020
  6. Johannes SixtDec 17, 2020
  7. Felipe ContrerasDec 17, 2020
  8. Johannes SixtDec 17, 2020
  9. Felipe ContrerasDec 18, 2020
  10. Seth HouseDec 17, 2020
  11. Felipe ContrerasDec 17, 2020
  12. Seth HouseDec 17, 2020
  13. Junio C HamanoDec 17, 2020
  14. Felipe ContrerasDec 18, 2020
  15. Felipe ContrerasDec 18, 2020
  16. Seth HouseDec 18, 2020
  17. Felipe ContrerasDec 18, 2020
  18. Seth HouseDec 18, 2020
  19. Felipe ContrerasDec 18, 2020
  20. Seth HouseDec 19, 2020
  21. Felipe ContrerasDec 19, 2020
  22. Junio C HamanoDec 19, 2020
  23. Felipe ContrerasDec 19, 2020
  24. Junio C HamanoDec 19, 2020
  25. Felipe ContrerasDec 19, 2020
  26. Seth HouseDec 21, 2020
  27. Felipe ContrerasDec 21, 2020
  28. Seth HouseDec 21, 2020
  29. Felipe ContrerasDec 21, 2020
  30. David AguilarDec 21, 2020
  31. Code of conduct violation?Felipe Contreras, Dec 21, 2020
  32. Junio C HamanoDec 22, 2020
  33. Felipe ContrerasDec 22, 2020
  34. Pratyush YadavDec 22, 2020
  35. Felipe ContrerasDec 23, 2020
  36. Junio C HamanoDec 23, 2020
  37. Felipe ContrerasDec 23, 2020
  38. Nobody is THE one making contributionJunio C Hamano, Dec 23, 2020
  39. Felipe ContrerasDec 23, 2020
  40. Junio C HamanoDec 23, 2020
  41. Felipe ContrerasDec 24, 2020
  42. Ævar Arnfjörð BjarmasonDec 24, 2020
  43. Felipe ContrerasDec 24, 2020
  44. Ævar Arnfjörð BjarmasonDec 24, 2020
  45. Felipe ContrerasDec 24, 2020
  46. Junio C HamanoDec 24, 2020
  47. Felipe ContrerasDec 27, 2020
  48. Junio C HamanoDec 27, 2020
  49. Felipe ContrerasDec 27, 2020
  50. Junio C HamanoDec 28, 2020
  51. Felipe ContrerasDec 28, 2020
  52. Randall S. BeckerDec 24, 2020
  53. Felipe ContrerasDec 24, 2020
  54. Junio C HamanoDec 24, 2020
  55. David AguilarDec 24, 2020
  56. Felipe ContrerasDec 24, 2020
  57. Junio C HamanoDec 18, 2020
  58. Felipe ContrerasDec 18, 2020
  59. Junio C HamanoDec 19, 2020
  60. Felipe ContrerasDec 19, 2020
  61. David AguilarDec 20, 2020
  62. Felipe ContrerasDec 20, 2020
  63. David AguilarDec 20, 2020
  64. Felipe ContrerasDec 21, 2020
  65. Seth HouseDec 19, 2020
  66. Felipe ContrerasDec 16, 2020
  67. Junio C HamanoDec 17, 2020
  68. Felipe ContrerasDec 17, 2020
  69. mergetool: use resolved conflicts in all the viewsFelipe Contreras, Dec 17, 2020
  70. Felipe ContrerasDec 21, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.