From: Michael Witten <mfwitten@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH RFC3 INTRO] I hope this will do it!
Date: Mon, 13 Apr 2009 13:23:44 -0500 [thread overview]
Message-ID: <1239647037-15381-1-git-send-email-mfwitten@gmail.com> (raw)
Here is the list of notable improvements:
send-email: --compose takes optional argument to existing file
* Update docs about what editor is chosen.
* Better variable name for --compose paths and filehandles.
* Abort on empty summary.
* Note (in commit message) that editing the final version no longer is used.
send-email: Minor cleanup of $smtp_server usage and send_message()
* Back to localhost.
* Add note about empty string if it's not already there.
send-email: Add --sleep for email throttling
* Put docs in alphabetical order.
send-email: Remove horrible mix of tabs and spaces
* Less verbose whitespace comment.
send-email: References: should only reference what is actually sent
* s/of/if/ (comment above send_message()).
send-email: Handle "GIT:" rather than "GIT: " during --compose
* Undo refactoring of get_patch_subject().
send-email: --smtp-server-port should take an integer
* Update documents to suggest that symbolic ports can be used.
* Put this commit with the docs.
send-email: Cleanup the usage text and docs a bit
* Add note about symbolic ports
Docs: send-email: Remove superfluous information in CONFIGURATION
* Remove comment block?
Docs: send-email: Put options back into alphabetical order
* Remove comment block?
The overall diffstat:
Documentation/git-send-email.txt | 129 ++++++---
git-send-email.perl | 641 +++++++++++++++++++++++++-------------
2 files changed, 511 insertions(+), 259 deletions(-)
The overall patch series:
[PATCH RFC3 01/13] Docs: send-email: Put options back into alphabetical order
new [PATCH RFC3 02/13] Docs: send-email: Refer to CONFIGURATION section for sendemail.multiedit
[PATCH RFC3 03/13] Docs: send-email: Remove superfluous information in CONFIGURATION
[PATCH RFC3 04/13] Docs: send-email: --smtp-server-port can take symbolic ports
[PATCH RFC3 05/13] send-email: Cleanup the usage text and docs a bit
[PATCH RFC3 06/13] send-email: Handle "GIT:" rather than "GIT: " during --compose
[PATCH RFC3 07/13] send-email: 'References:' should only reference what is sent
new [PATCH RFC3 08/13] send-email: Remove superfluous `my $editor = ...'
[PATCH RFC3 09/13] send-email: Remove horrible mix of tabs and spaces
[PATCH RFC3 10/13] send-email: Add --sleep for email throttling
[PATCH RFC3 11/13] send-email: Minor cleanup of $smtp_server usage and send_message()
[PATCH RFC3 12/13] send-email: --compose takes optional argument to existing file
new [PATCH RFC3 13/13] send-email: --compose always includes a 'GIT: ' prefixed list of patch subjects
Sincerely,
Michael Witten
next reply other threads:[~2009-04-13 18:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 18:23 Michael Witten [this message]
2009-04-13 18:23 ` [PATCH RFC3 01/13] Docs: send-email: Put options back into alphabetical order Michael Witten
2009-04-13 18:23 ` [PATCH RFC3 02/13] Docs: send-email: Refer to CONFIGURATION section for sendemail.multiedit Michael Witten
2009-04-13 18:23 ` [PATCH RFC3 03/13] Docs: send-email: Remove superfluous information in CONFIGURATION Michael Witten
2009-04-13 18:23 ` [PATCH RFC3 04/13] Docs: send-email: --smtp-server-port can take symbolic ports Michael Witten
2009-04-13 18:23 ` [PATCH RFC3 05/13] send-email: Cleanup the usage text and docs a bit Michael Witten
2009-04-13 18:23 ` [PATCH RFC3 06/13] send-email: Handle "GIT:" rather than "GIT: " during --compose Michael Witten
2009-04-13 18:23 ` [PATCH RFC3 07/13] send-email: 'References:' should only reference what is sent Michael Witten
2009-04-13 18:23 ` [PATCH RFC3 08/13] send-email: Remove superfluous `my $editor = ...' Michael Witten
2009-04-13 18:23 ` [PATCH RFC3 09/13] send-email: Remove horrible mix of tabs and spaces Michael Witten
2009-04-13 18:23 ` [PATCH RFC3 10/13] send-email: Add --sleep for email throttling Michael Witten
2009-04-13 18:23 ` [PATCH RFC3 11/13] send-email: Minor cleanup of $smtp_server usage and send_message() Michael Witten
2009-04-13 18:23 ` [PATCH RFC3 12/13] send-email: --compose takes optional argument to existing file Michael Witten
2009-04-13 18:23 ` [PATCH RFC3 13/13] send-email: --compose always includes a 'GIT: ' prefixed list of patch subjects Michael Witten
2009-04-13 20:55 ` [PATCH RFC3 09/13] send-email: Remove horrible mix of tabs and spaces Junio C Hamano
2009-04-13 22:49 ` Michael Witten
2009-04-14 5:31 ` Andreas Ericsson
2009-04-14 6:19 ` Junio C Hamano
2009-04-14 7:17 ` Andreas Ericsson
2009-04-14 7:03 ` Michael Witten
2009-04-14 7:38 ` Andreas Ericsson
2009-04-13 23:39 ` [PATCH RFC3 08/13] send-email: Remove superfluous `my $editor = ...' Stephen Boyd
2009-04-14 0:41 ` Michael Witten
2009-04-14 0:43 ` Michael Witten
2009-04-14 6:16 ` Björn Steinbrink
2009-04-14 8:51 ` Junio C Hamano
2009-04-13 20:51 ` [PATCH RFC3 05/13] send-email: Cleanup the usage text and docs a bit Junio C Hamano
2009-04-13 22:42 ` Michael Witten
2009-04-14 5:39 ` Junio C Hamano
2009-04-14 6:00 ` Michael Witten
2009-04-14 6:46 ` Junio C Hamano
2009-04-14 7:15 ` Michael Witten
2009-04-13 20:45 ` [PATCH RFC3 03/13] Docs: send-email: Remove superfluous information in CONFIGURATION Junio C Hamano
2009-04-13 22:30 ` Michael Witten
2009-04-13 18:45 ` [PATCH RFC3 INTRO] I hope this will do it! Michael Witten
2009-04-14 9:02 ` Junio C Hamano
2009-04-14 16:26 ` Michael Witten
2009-04-14 18:47 ` Junio C Hamano
2009-04-14 18:50 ` Michael Witten
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1239647037-15381-1-git-send-email-mfwitten@gmail.com \
--to=mfwitten@gmail.com \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).