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

Re: [PATCH] send-email: new option to walkaround email server limits

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
May 4, 2017, 02:18 UTC
Message-ID
<CALkWK0kceHMyjuKvTa=CQZsGnXKaUuG6=G-HxEFSHaN+dqe6nw@mail.gmail.com>
In-Reply-To
<xmqqk25xct1w.fsf@gitster.mtv.corp.google.com>
For the list, in plain text:

IIUC, they use the date received to sort. I think this might stem from a historical cruft: emails sometimes took non-trivial amounts of time to transit, back in the old days. MUAs (especially web-based ones) probably did not want to violate user expectation by placing a new email under several already-read emails. I would argue that this was reasonable behavior. Further, since email is near-instantaneous today, it really makes no difference which way the MUA sorts. Except for git send-email.

It might be acceptable to put in a "practical hack" to help out MUAs in the context of "near instant forwarding". I would argue against it on grounds of it being an ugly hack, for very little benefit. The patch that began this thread is also ugly, but has the important consequence of enabling some people to use git send-email at all.

p.s- We should probably allow emails from mobile devices on the list. It usually contains a HTML subpart.

Previous: Junio C HamanoNext: Ævar Arnfjörð Bjarmason
Message 6 of 9 in “send-email: new option to walkaround email server limits”
  1. send-email: new option to walkaround email server limitsxiaoqiang zhao, Apr 29, 2017
  2. Junio C HamanoMay 1, 2017
  3. 赵小强May 1, 2017
  4. Ævar Arnfjörð BjarmasonMay 2, 2017
  5. Junio C HamanoMay 4, 2017
  6. Ramkumar RamachandraMay 4, 2017
  7. Ævar Arnfjörð BjarmasonMay 4, 2017
  8. Paolo BonziniMay 2, 2017
  9. 赵小强May 4, 2017

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.