delta/git.git/git-send-email.perl, branch sg/completion

i18n: send-email: mark composing message for translation

2016-12-14T19:00:06+00:00

When composing an e-mail, there is a message for the user whose lines
begin in "GIT:" that can be marked for translation.

Signed-off-by: Vasco Almeida 
Signed-off-by: Junio C Hamano

i18n: send-email: mark string with interpolation for translation

2016-12-14T19:00:06+00:00

Mark warnings, errors and other messages that are interpolated for
translation.

We call sprintf() before calling die() and in few other circumstances in
order to replace the values on the placeholders.

Signed-off-by: Vasco Almeida 
Signed-off-by: Junio C Hamano

i18n: send-email: mark warnings and errors for translation

2016-12-14T19:00:05+00:00

Mark warnings, errors and other messages for translation.

Signed-off-by: Vasco Almeida 
Signed-off-by: Junio C Hamano

i18n: send-email: mark strings for translation

2016-12-14T19:00:05+00:00

Mark strings often displayed to the user for translation.

Signed-off-by: Vasco Almeida 
Signed-off-by: Junio C Hamano

Merge branch 'jc/send-email-skip-backup'

2016-07-11T17:31:04+00:00

A careless invocation of "git send-email directory/" after editing
0001-change.patch with an editor often ends up sending both
0001-change.patch and its backup file, 0001-change.patch~, causing
embarrassment and a minor confusion.  Detect such an input and
offer to skip the backup files when sending the patches out.

* jc/send-email-skip-backup:
  send-email: detect and offer to skip backup files

Merge branch 'jd/send-email-to-whom'

2016-05-03T21:08:16+00:00

A question by "git send-email" to ask the identity of the sender
has been updated.

* jd/send-email-to-whom:
  send-email: fix grammo in the prompt that asks e-mail recipients

send-email: fix grammo in the prompt that asks e-mail recipients

2016-04-25T20:35:38+00:00

The message, which dates back to the very original version 83b24437
made in 2005, sounds clumsy, grammatically incorrect, and is hard to
understand.

Reported-by: John Darrington 
Signed-off-by: Junio C Hamano

Merge branch 'ew/send-email-drop-data-dumper'

2016-04-22T22:45:06+00:00

Code clean-up.

* ew/send-email-drop-data-dumper:
  send-email: do not load Data::Dumper

Merge branch 'ew/send-email-readable-message-id'

2016-04-22T22:45:05+00:00

"git send-email" now uses a more readable timestamps when
formulating a message ID.

* ew/send-email-readable-message-id:
  send-email: more meaningful Message-ID

send-email: detect and offer to skip backup files

2016-04-13T01:45:45+00:00

Diligent people save output from format-patch to files, proofread
and edit them and then finally send the result out.  If the
resulting files are sent out with "git send-email 0*", this ends up
sending backup files (e.g. 0001-X.patch.backup or 0001-X.patch~)
left by their editors next to the final version.  Sending them with
"git send-email 0*.patch" (if format-patch was run with the standard
suffix) would avoid such an embarrassment, but not everybody is
careful.

After collecting files to be sent (and sorting them if read from a
directory), notice when the file being sent out has the same name as
the previous file, plus some suffix (e.g. 0001-X.patch was sent, and
we are looking at 0001-X.patch.backup or 0001-X.patch~), and the
suffix begins with a non-alnum (e.g. ".backup" or "~") and ask if
the user really wants to send it out.  Once the user skips sending
such a "backup" file, remember the suffix and stop asking the same
question (e.g. after skipping 0001-X.patch~, skip 0002-Y.patch~
without asking).

Signed-off-by: Junio C Hamano