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

Re: [GSoC] A late proposal: a modern send-email

From
惠轶群 <huiyiqun@gmail.com>
Date
Mar 26, 2016, 10:18 UTC
Message-ID
<CAKqreuyb1D7_D9iGWAqnLFc9ERsmEM-nu0LWdg1P4u7+aV6zGQ@mail.gmail.com>
In-Reply-To
<CAKqreuyN--AjjhTcTx1+Baec=j-6TJPj8Rwoxre86TJp2UMGDg@mail.gmail.com>
To make it clearer:
1. there are so many great mail clients, why not let these experts to handle the
    dispatch of mail?

For example, as a One-time-password user of gmail, I have to generate an app password for each terminal device I'd like to send patch on.

It's more important that I could not use my favorite mail client which has contact list, familiar interface and more personal configuration.

Why not let one program just do one thing and do it best?

In my opinion, `mailto` is a suitable method. git is one of the best version control systems. So it forms basic structure of the mail according to the patches and passes it to the best mail client. How amazing.

2. But this workload is not enough for whole summer. I thought I could do other
    interesting things based on the `mailto` link.
mail client is a straightforward choice.

In fact, I meant to implement an interface more friendly to new users. no matter how it is implemented or what it is based on. The first time I send patch via gmail is not a happy memory.

Previous: 惠轶群Next: 惠轶群
Message 6 of 15 in “[GSoC] A late proposal: a modern send-email”
  1. 惠轶群Mar 25, 2016
  2. Junio C HamanoMar 25, 2016
  3. 惠轶群Mar 26, 2016
  4. Pranit BauvaMar 26, 2016
  5. 惠轶群Mar 26, 2016
  6. 惠轶群Mar 26, 2016
  7. 惠轶群Mar 26, 2016
  8. Ævar Arnfjörð BjarmasonMar 28, 2016
  9. 惠轶群Mar 29, 2016
  10. Ævar Arnfjörð BjarmasonMar 29, 2016
  11. Johannes SchindelinMar 30, 2016
  12. Eric WongMar 27, 2016
  13. Javier Domingo CansinoMar 27, 2016
  14. 惠轶群Mar 28, 2016
  15. Eric WongApr 5, 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.