From: Junio C Hamano <gitster@pobox.com>
To: 惠轶群 <huiyiqun@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [GSoC] A late proposal: a modern send-email
Date: Fri, 25 Mar 2016 11:16:12 -0700 [thread overview]
Message-ID: <xmqqzitm2zkj.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAKqreuyC8p9m_dgVpXCiT_hf=8qBA_5kZ5NABQGx0QDOiCBbww@mail.gmail.com> ("惠轶群"'s message of "Sat, 26 Mar 2016 01:59:08 +0800")
惠轶群 <huiyiqun@gmail.com> writes:
> # Purpose
> The current implementation of send-email is based on perl and has only
> a tui, it has two problems:
> - user must install a ton of dependencies before submit a single patch.
> - tui and parameter are both not quite friendly to new users.
Is "a ton of dependencies" true? "apt-cache show git-email"
suggests otherwise. Is "a ton of dependencies" truly a problem?
"apt-get install" would resolve the dependencies for you.
> # Plan
> So I propose to implement following:
> - Allow user to send mail via a [`mailto`
> link](https://en.wikipedia.org/wiki/Mailto). so that users could
> complete the mail in their favorite email clients such as gmail, mutt,
> alpine and even gmail for android through
IIRC, GMail on Android is incapable of sending a "text/plain", so
that part may not fly well.
> - Build a simple email client (maybe a web components based web app or
> wxwidgets based GUI client, they are both cross-platform) which is
> easy to use for sending patch without disrupting the mailbox format.
I suspect it would yield a better result if the plan were to update
a popular email client and make it possible to tell it to read an
existing text file (i.e. mbox) without corrupting its contents.
People do not have to learn a new mail client if done that way.
That may not be a "Git" project, but GSoC is not limited to Git ;-)
next prev parent reply other threads:[~2016-03-25 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 17:59 [GSoC] A late proposal: a modern send-email 惠轶群
2016-03-25 18:16 ` Junio C Hamano [this message]
2016-03-26 2:13 ` 惠轶群
2016-03-26 6:18 ` Pranit Bauva
2016-03-26 9:52 ` 惠轶群
2016-03-26 10:18 ` 惠轶群
2016-03-26 10:21 ` 惠轶群
2016-03-28 16:49 ` Ævar Arnfjörð Bjarmason
2016-03-29 4:17 ` 惠轶群
2016-03-29 23:47 ` Ævar Arnfjörð Bjarmason
2016-03-30 12:10 ` Johannes Schindelin
2016-03-27 22:00 ` Eric Wong
2016-03-27 23:31 ` Javier Domingo Cansino
2016-03-28 13:00 ` 惠轶群
2016-04-05 0:03 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqzitm2zkj.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=huiyiqun@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).