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

Re: Working with public-inbox.org [Was: [PATCH] rev-parse: respect core.hooksPath in --git-path]

From
AKArif Khokar <arif.i.khokar@gmail.com>
Date
Feb 14, 2017, 03:55 UTC
Message-ID
<acac96da-2404-4f7e-a83d-7648ca448d31@hotmail.com>
In-Reply-To
<xmqqefz1ew1h.fsf@gitster.mtv.corp.google.com>
On 02/13/2017 02:21 PM, Junio C Hamano wrote:
Show 13 quoted lines
> Arif Khokar <arif.i.khokar@gmail.com> writes:
>
>> ... I
>> still think it would be better to be able to list the message-id
>> values in the header or body of the cover letter message of a patch
>> series (preferably the former) in order to facilitate downloading the
>> patches via NNTP from gmane or public-inbox.org.
>
> You are looking at builtin/log.c::make_cover_letter()?  Patches
> welcome, but I think you'd need a bit of preparatory refactoring
> to allow gen_message_id() be called for all messages _before_ this
> function is called, as currently we generate them as we emit each
> patch.
Thank you for the advice; I'll look into it.

One concern I have regarding this idea is whether or not SMTP servers typically replace a Message-Id header set by the client. If that's the case, then this approach may unexpectedly fail for some people depending on what email provider they use (if they don't maintain their own MTA setup).

Show 7 quoted lines
>> Alternatively, or perhaps in addition to the list of message-ids, a
>> list of URLs to public-inbox.org or gmane messages could also be
>> provided for those who prefer to download patches via HTTP.
>
> Many people around here do not want to repeat the mistake of relying
> too much on one provider.  Listing Message-IDs may be a good idea,
> listing URLs that are tied to one provider is less so.

I agree. I've actually thought that it would be useful to mirror a read-only copy of the mailing list on a public newsgroup that could be accessed through a free provider such as eternal-september.org or the Google groups interface. It certainly would reduce the potential losing easy access to the archives of this email list if gmane and public-inbox.org fail. But I suspect doing something like that would potentially increase the spam volume substantially for regular participants/contributors.

Previous: Junio C HamanoNext: Junio C Hamano
Message 54 of 59 in “Working with public-inbox.org [Was: [PATCH] rev-parse: respect core.hooksPath in --git-path]”
  1. Stefan BellerAug 16, 2016
  2. Junio C HamanoAug 16, 2016
  3. Jeff KingAug 16, 2016
  4. Junio C HamanoAug 16, 2016
  5. Stefan BellerAug 16, 2016
  6. Junio C HamanoAug 16, 2016
  7. Eric WongAug 16, 2016
  8. Eric WongAug 16, 2016
  9. Johannes SchindelinAug 18, 2016
  10. Eric WongAug 18, 2016
  11. Junio C HamanoAug 18, 2016
  12. Johannes SchindelinAug 19, 2016
  13. Johannes SchindelinAug 19, 2016
  14. Stefan BellerAug 19, 2016
  15. Eric WongAug 19, 2016
  16. Johannes SchindelinAug 22, 2016
  17. Jeff KingAug 22, 2016
  18. Eric WongAug 19, 2016
  19. Johannes SchindelinAug 22, 2016
  20. Jakub NarębskiAug 22, 2016
  21. Johannes SchindelinAug 25, 2016
  22. Jakub NarębskiAug 28, 2016
  23. Johannes SchindelinAug 29, 2016
  24. Eric WongAug 22, 2016
  25. Johannes SchindelinAug 25, 2016
  26. Jakub NarębskiAug 27, 2016
  27. Johannes SchindelinAug 28, 2016
  28. Jakub NarębskiAug 28, 2016
  29. Johannes SchindelinAug 29, 2016
  30. Jeff KingAug 19, 2016
  31. Jakub NarębskiAug 20, 2016
  32. Johannes SchindelinAug 22, 2016
  33. Duy NguyenAug 22, 2016
  34. Philip OakleyAug 22, 2016
  35. Johannes SchindelinAug 24, 2016
  36. Eric WongAug 24, 2016
  37. Johannes SchindelinAug 25, 2016
  38. Jakub NarębskiAug 27, 2016
  39. Johannes SchindelinAug 28, 2016
  40. Announcing Git User's Survey 2016 [was: Working with public-inbox.org]Jakub Narębski, Aug 28, 2016
  41. Johannes SchindelinSep 9, 2016
  42. Jakub NarębskiSep 9, 2016
  43. Johannes SchindelinAug 24, 2016
  44. Eric WongAug 24, 2016
  45. Jeff KingAug 24, 2016
  46. Eric WongAug 24, 2016
  47. Johannes SchindelinFeb 10, 2017
  48. Arif KhokarFeb 13, 2017
  49. Johannes SchindelinFeb 13, 2017
  50. Arif KhokarFeb 14, 2017
  51. Arif KhokarFeb 14, 2017
  52. Eric WongFeb 14, 2017
  53. Junio C HamanoFeb 13, 2017
  54. Arif KhokarFeb 14, 2017
  55. Junio C HamanoFeb 14, 2017
  56. Arif KhokarFeb 14, 2017
  57. Jeff KingFeb 14, 2017
  58. Johannes SchindelinAug 25, 2016
  59. Johannes SchindelinAug 26, 2016

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.