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

Deprecation/Removal schedule

From
Junio C Hamano <junkio@cox.net>
Date
Feb 5, 2007, 06:48 UTC
Message-ID
<7v8xfdnlqm.fsf@assigned-by-dhcp.cox.net>

We seem to have accumulated some crufts, duplicated and/or disused features. I think we should start planning deprecation and removal.

Here are potential candidates we might want to mark as "scheduled for removal". Note that I threw in a bit more than what I seriously consider bloat, so your favorite may appear in the list.

* git-applymbox and git-applypatch
  Does anybody rely on them?  I think new users are all using
  git-am (this is just what _I_ think -- please consider this
  message as a poll to voice your objection).
* git-whatchanged
  This has been identical to git-log with different default
  options.
* git-p4import, git-quiltimport and contrib/gitview
  These have seen almost no activity since their appearance.  It
  could be that they are already perfect and many people are
  using them happily, but I find it a bit hard to believe.
* git-diff-stages
  Judging from the fact that nobody complained what it does is
  not accessible from "git diff" wrapper, I suspect nobody is
  interested in comparing the stages while merging (I certainly
  do not use it myself).
* git-lost-found
  Although it has served us well, I think it is about to outlive
  its usefulness, thanks to the recent "reflog by default"
  change.
* git-local-fetch, git-ssh-fetch and git-ssh-upload
  In-tree git-fetch does not use these commit walkers as the
  backend.  They might be used by Cogito and people's scripts so
  I am not seriously pushing for their removal.  http-fetch is
  here to stay so it's not like removing them would reduce the
  burden to maintain the commit walkers anyway.
* contrib/colordiff
  This has long outlived its usefulness.
Next: Shawn O. Pearce
Message 1 of 36 in “Deprecation/Removal schedule”
  1. Junio C HamanoFeb 5, 2007
  2. Shawn O. PearceFeb 5, 2007
  3. Jakub NarebskiFeb 5, 2007
  4. Jakub NarebskiFeb 5, 2007
  5. Shawn O. PearceFeb 5, 2007
  6. Alex RiesenFeb 5, 2007
  7. Shawn O. PearceFeb 5, 2007
  8. Alex RiesenFeb 5, 2007
  9. Shawn O. PearceFeb 5, 2007
  10. Alex RiesenFeb 6, 2007
  11. Johannes SchindelinFeb 6, 2007
  12. Jeff KingFeb 6, 2007
  13. Johannes SchindelinFeb 6, 2007
  14. Alex RiesenFeb 6, 2007
  15. Johannes SchindelinFeb 6, 2007
  16. Alex RiesenFeb 6, 2007
  17. Alex RiesenFeb 6, 2007
  18. Mark WoodingFeb 5, 2007
  19. Johannes SchindelinFeb 5, 2007
  20. Alex RiesenFeb 5, 2007
  21. Linus TorvaldsFeb 5, 2007
  22. Junio C HamanoFeb 5, 2007
  23. Add --patchdepth parameter to git-am.shAndy Parkins, Feb 5, 2007
  24. Shawn O. PearceFeb 5, 2007
  25. Junio C HamanoFeb 7, 2007
  26. Jakub NarebskiFeb 7, 2007
  27. Andy ParkinsFeb 7, 2007
  28. Andreas EricssonFeb 6, 2007
  29. Alex RiesenFeb 6, 2007
  30. Johannes SchindelinFeb 6, 2007
  31. Junio C HamanoFeb 7, 2007
  32. Jakub NarebskiFeb 7, 2007
  33. Johannes SchindelinFeb 7, 2007
  34. Jakub NarebskiFeb 7, 2007
  35. Junio C HamanoFeb 7, 2007
  36. Johannes SchindelinFeb 7, 2007

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.