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

Re: [PATCH] remote-helpers: point at their upstream repositories

From
Jeff King <peff@peff.net>
Date
May 16, 2014, 08:41 UTC
Message-ID
<20140516084126.GB21468@sigill.intra.peff.net>
In-Reply-To
<xmqqa9aid52a.fsf@gitster.dls.corp.google.com>
On Thu, May 15, 2014 at 03:56:29PM -0700, Junio C Hamano wrote:
> Two announcements for their version 0.2 on the list archive are not
> quite enough to advertise them to their users.

I do not think this README nor a mention in the release notes will get their attention either, and many people (and packagers) will continue to use the stale versions forever until those versions go away.

I would much rather _replace_ them with a README in the long run, and people will notice that they are gone, and then use the README to update their install procedure.

For 2.0, I am hesitant to do that, though I do not have a problem with a README like this as a heads-up to prepare packagers for the future. I say hesitant because people may have been test-packaging 2.0.0-rc3 in preparation for release, and it will be annoying to them to suddenly switch.

But that being said, this is Felipe's code. While we have a legal right to distribute it in v2.0, if he would really prefer it out for v2.0, I would respect that.

I would prefer to instrument the code with warnings, as that is the sort of thing a packager moving from -rc3 to -final might not notice, and shipping the warnings to end users who did not package the software in the first place will not help them. It is the attention of the packagers (and source-builders) you want to get.

Of course that is all just my two cents, and is mostly predicated on there _being_ packagers of the contrib/ tools. It looks like there is a Debian package in RFP status, but I don't know if that is following the new release closely. And I don't know about other systems.

-Peff
Previous: Felipe ContrerasNext: Paolo Ciarrocchi
Message 3 of 40 in “remote-helpers: point at their upstream repositories”
  1. remote-helpers: point at their upstream repositoriesJunio C Hamano, May 15, 2014
  2. Felipe ContrerasMay 16, 2014
  3. Jeff KingMay 16, 2014
  4. Paolo CiarrocchiMay 16, 2014
  5. Jeff KingMay 16, 2014
  6. Felipe ContrerasMay 16, 2014
  7. Felipe ContrerasMay 16, 2014
  8. Junio C HamanoMay 16, 2014
  9. Felipe ContrerasMay 16, 2014
  10. James DenholmMay 17, 2014
  11. Felipe ContrerasMay 17, 2014
  12. James DenholmMay 18, 2014
  13. Felipe ContrerasMay 18, 2014
  14. Junio C HamanoMay 18, 2014
  15. Felipe ContrerasMay 19, 2014
  16. Junio C HamanoMay 19, 2014
  17. Michael HaggertyMay 20, 2014
  18. Johan HerlandMay 20, 2014
  19. Felipe ContrerasMay 20, 2014
  20. Felipe ContrerasMay 20, 2014
  21. Jeff KingMay 16, 2014
  22. Felipe ContrerasMay 17, 2014
  23. Jeff KingMay 17, 2014
  24. Felipe ContrerasMay 17, 2014
  25. Matthieu MoyMay 18, 2014
  26. Felipe ContrerasMay 18, 2014
  27. Junio C HamanoMay 18, 2014
  28. Felipe ContrerasMay 19, 2014
  29. Junio C HamanoMay 19, 2014
  30. Felipe ContrerasMay 19, 2014
  31. Junio C HamanoMay 19, 2014
  32. Junio C HamanoMay 19, 2014
  33. Felipe ContrerasMay 20, 2014
  34. Junio C HamanoMay 20, 2014
  35. Junio C HamanoMay 19, 2014
  36. Felipe ContrerasMay 20, 2014
  37. Junio C HamanoMay 20, 2014
  38. Felipe ContrerasMay 20, 2014
  39. Junio C HamanoMay 20, 2014
  40. Junio C HamanoMay 16, 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.