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

Re: backwards compatibility, was Re: [PATCH v1 1/3] Introduce config variable "diff.primer"

From
Jeff King <peff@peff.net>
Date
Jan 26, 2009, 11:16 UTC
Message-ID
<20090126111605.GB19993@coredump.intra.peff.net>
In-Reply-To
<alpine.DEB.1.00.0901261154330.14855@racer>
On Mon, Jan 26, 2009 at 11:59:46AM +0100, Johannes Schindelin wrote:
Show 7 quoted lines
> Just a reminder: we are very conservative when it comes to breaking 
> backwards compatibility.  For example, people running (but not upgrading) 
> gitweb who want to upgrade Git may rightfully expect their setups not to 
> be broken for a long time, if ever.
> 
> So your mentioning gitweb using "git diff" precludes all kind of cute 
> games, methinks.

Are you aware that gitweb no longer calls "git diff", exactly because of problems caused by calling a porcelain from a script?

I don't want to break existing setups, either. But at some point you have to say "this is porcelain, so don't rely on there not being any user-triggered effects in its behavior". If porcelain is cast in stone, then what is the point in differentiating plumbing from porcelain?

And when the line is blurred (as I think it is in several places), then it has to be dealt with on a case-by-case basis. What is the benefit, and what is the likelihood and extent of harm?

Show 6 quoted lines
> And please no "anybody who would do this and that would be nuts" excuses: 
> if you want to change something fundamental like this, _you_ have to 
> defend it.
> 
> It is not acceptable to just shout out what you want and expect those 
> affected negatively to do the impact analysis for you.

This message is addressed to me, but I don't know exactly what you think I'm proposing, failing to defend, or failing to do an impact analysis for. Or are you speaking generally of the "you" who submit patches?

-Peff
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 26 of 41 in “Introduce config variable "diff.primer"”
  1. 0/3 Introduce config variable "diff.primer"Keith Cascio, Jan 25, 2009
  2. 1/3 Introduce config variable "diff.primer"Keith Cascio, Jan 25, 2009
  3. 2/3 Test functionality of new config variable "diff.primer"Keith Cascio, Jan 25, 2009
  4. 3/3 git-gui hooks for new config variable "diff.primer"Keith Cascio, Jan 25, 2009
  5. Johannes SchindelinJan 25, 2009
  6. Keith CascioJan 25, 2009
  7. Johannes SchindelinJan 25, 2009
  8. Keith CascioJan 25, 2009
  9. Johannes SchindelinJan 25, 2009
  10. Keith CascioJan 25, 2009
  11. Jeff KingJan 25, 2009
  12. Keith CascioJan 25, 2009
  13. Jeff KingJan 25, 2009
  14. Junio C HamanoJan 25, 2009
  15. Junio C HamanoJan 26, 2009
  16. Keith CascioJan 26, 2009
  17. Jeff KingJan 26, 2009
  18. Junio C HamanoJan 26, 2009
  19. Keith CascioJan 26, 2009
  20. Jeff KingJan 26, 2009
  21. Junio C HamanoJan 26, 2009
  22. Jeff KingJan 26, 2009
  23. Johannes SchindelinJan 26, 2009
  24. Jeff KingJan 26, 2009
  25. backwards compatibility, was Re: [PATCH v1 1/3] Introduce config variable "diff.primer"Johannes Schindelin, Jan 26, 2009
  26. Jeff KingJan 26, 2009
  27. Johannes SchindelinJan 26, 2009
  28. Jeff KingJan 26, 2009
  29. Keith CascioJan 27, 2009
  30. Jay SoffianJan 26, 2009
  31. Jeff KingJan 26, 2009
  32. Jay SoffianJan 26, 2009
  33. Junio C HamanoJan 26, 2009
  34. Jay SoffianJan 26, 2009
  35. Jeff KingJan 26, 2009
  36. Junio C HamanoJan 26, 2009
  37. Junio C HamanoJan 25, 2009
  38. Keith CascioJan 25, 2009
  39. Jeff KingJan 25, 2009
  40. Keith CascioJan 27, 2009
  41. Jeff KingJan 27, 2009

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.