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

Re: [PATCH 0/4] remote-hg: more improvements

From
Junio C Hamano <gitster@pobox.com>
Date
May 14, 2014, 22:34 UTC
Message-ID
<xmqq1tvwhtvm.fsf@gitster.dls.corp.google.com>
In-Reply-To
<87a9akro14.fsf@fencepost.gnu.org>
David Kastrup <dak@gnu.org> writes:
Show 14 quoted lines
>>> I'm not entirely convinced of that: there is something akin to drop-dead
>>> gorgeous code: code that is so well done that it would not matter with
>>> regard to its maintenance whether or not its author dropped dead because
>>> it's both done well as well as documented in a manner where the original
>>> author could not offer significant additional help.
>>
>> I would have to say that you are living in a fantasy land.  During
>> the entire life of Git, I do not think I ever saw such a code that
>> is perfect from the get-go and did not require any maintenance to
>> adjust to the changing time.
>
> You are attacking a straw man.  "where the original author could not
> offer significant _additional_ help" does not at all equate "does not
> require any maintenance".

Ahh, I realize that I misread what you wrote. Yes, I do agree with you that we have a lot of pieces of code, with log messages we can find with the help of blame, that the author himself does not need to be present for them to be maintained properly. Making all the code in Git like that may be an unattainable goal, but calling the effort to make that happen "living in a fantasy land" is utterly wrong. Sorry about confusion.

Previous: David KastrupNext: Junio C Hamano
Message 38 of 49 in “remote-hg: more improvements”
  1. 0/4 remote-hg: more improvementsFelipe Contreras, May 4, 2014
  2. 1/4 remote-hg: add more testsFelipe Contreras, May 4, 2014
  3. Eric SunshineMay 4, 2014
  4. 2/4 t: remote-hg: add file operation testsFelipe Contreras, May 4, 2014
  5. 3/4 t: remote-hg: trivial cleanups and fixesFelipe Contreras, May 4, 2014
  6. 4/4 remote-hg: add support for hg v3.0Felipe Contreras, May 4, 2014
  7. Junio C HamanoMay 7, 2014
  8. Felipe ContrerasMay 7, 2014
  9. Junio C HamanoMay 7, 2014
  10. Felipe ContrerasMay 7, 2014
  11. Junio C HamanoMay 7, 2014
  12. Felipe ContrerasMay 8, 2014
  13. James DenholmMay 8, 2014
  14. Felipe ContrerasMay 8, 2014
  15. Philippe VaucherMay 11, 2014
  16. Philippe VaucherMay 12, 2014
  17. Junio C HamanoMay 12, 2014
  18. Felipe ContrerasMay 12, 2014
  19. Junio C HamanoMay 12, 2014
  20. Felipe ContrerasMay 12, 2014
  21. Philippe VaucherMay 14, 2014
  22. David KastrupMay 14, 2014
  23. Philippe VaucherMay 14, 2014
  24. David KastrupMay 14, 2014
  25. Philippe VaucherMay 14, 2014
  26. David KastrupMay 14, 2014
  27. Philippe VaucherMay 14, 2014
  28. David KastrupMay 14, 2014
  29. Philippe VaucherMay 14, 2014
  30. Felipe ContrerasMay 14, 2014
  31. David KastrupMay 14, 2014
  32. Felipe ContrerasMay 14, 2014
  33. David KastrupMay 14, 2014
  34. Felipe ContrerasMay 14, 2014
  35. David KastrupMay 15, 2014
  36. Junio C HamanoMay 14, 2014
  37. David KastrupMay 14, 2014
  38. Junio C HamanoMay 14, 2014
  39. Junio C HamanoMay 8, 2014
  40. Felipe ContrerasMay 8, 2014
  41. Junio C HamanoMay 8, 2014
  42. Felipe ContrerasMay 8, 2014
  43. Junio C HamanoMay 8, 2014
  44. Felipe ContrerasMay 8, 2014
  45. Junio C HamanoMay 8, 2014
  46. Felipe ContrerasMay 8, 2014
  47. Felipe ContrerasMay 9, 2014
  48. Junio C HamanoMay 9, 2014
  49. Felipe ContrerasMay 9, 2014

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.