<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/git-send-email.perl, branch v2.46.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.46.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.46.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2024-07-16T18:18:56Z</updated>
<entry>
<title>Merge branch 'cb/send-email-sanitize-trailer-addresses'</title>
<updated>2024-07-16T18:18:56Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2024-07-16T18:18:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=f4c6a0e27548352f131af58bef079bd6c85268f6'/>
<id>urn:sha1:f4c6a0e27548352f131af58bef079bd6c85268f6</id>
<content type='text'>
Address-looking strings found on the trailer are now placed on the
Cc: list after running through sanitize_address by "git send-email".

* cb/send-email-sanitize-trailer-addresses:
  git-send-email: use sanitized address when reading mbox body
</content>
</entry>
<entry>
<title>git-send-email: use sanitized address when reading mbox body</title>
<updated>2024-07-01T18:38:29Z</updated>
<author>
<name>Csókás, Bence</name>
<email>csokas.bence@prolan.hu</email>
</author>
<published>2024-07-01T09:01:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=c852531f451331eb9d5ba57d154b0e150246a438'/>
<id>urn:sha1:c852531f451331eb9d5ba57d154b0e150246a438</id>
<content type='text'>
Addresses that are mentioned on the trailers in the commit log
messages (e.g., "Reviewed-by") are added to the "Cc:" list by "git
send-email".  These hand-written addresses, however, may be
malformed (e.g., having unquoted "." and other punctutation marks in
the display-name part) and can upset MTA.

The code does use the sanitize_address() helper on these
address-looking strings to turn them into valid addresses, but it is
used only to see if the address should be suppressed.  The original
string taken from the message is added to the @cc list if the code
decides the address is not suppressed.

Because the addresses on trailer lines are hand-written and more
likely to contain malformed addresses, when adding to the @cc list,
use the result from sanitize_address, not the original.  Note that
we do not modify the behaviour for addresses taken from the e-mail
headers, as they are more likely to be machine generated and
well-formed.

Signed-off-by: Csókás, Bence &lt;csokas.bence@prolan.hu&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>send-email: move newline characters out of a few translatable strings</title>
<updated>2024-04-10T16:11:10Z</updated>
<author>
<name>Dragan Simic</name>
<email>dsimic@manjaro.org</email>
</author>
<published>2024-04-10T07:01:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=c02dc38570958a7e4f4c9c31663fbf19f5097601'/>
<id>urn:sha1:c02dc38570958a7e4f4c9c31663fbf19f5097601</id>
<content type='text'>
Move the already existing newline characters out of a few translatable
strings, to help a bit with the translation efforts.

Signed-off-by: Dragan Simic &lt;dsimic@manjaro.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'tz/send-email-negatable-options'</title>
<updated>2023-12-10T00:37:51Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2023-12-10T00:37:51Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=1ef1cce9c254d3787586ac87c1d1a2ca2c00bfd3'/>
<id>urn:sha1:1ef1cce9c254d3787586ac87c1d1a2ca2c00bfd3</id>
<content type='text'>
Newer versions of Getopt::Long started giving warnings against our
(ab)use of it in "git send-email".  Bump the minimum version
requirement for Perl to 5.8.1 (from September 2002) to allow
simplifying our implementation.

* tz/send-email-negatable-options:
  send-email: avoid duplicate specification warnings
  perl: bump the required Perl version to 5.8.1 from 5.8.0
</content>
</entry>
<entry>
<title>Merge branch 'tz/send-email-helpfix'</title>
<updated>2023-11-20T00:57:22Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2023-11-20T00:57:22Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e9eb93bb2a01c7d3468159a9606ba8c73e0791f0'/>
<id>urn:sha1:e9eb93bb2a01c7d3468159a9606ba8c73e0791f0</id>
<content type='text'>
Typoes in "git send-email -h" have been corrected.

* tz/send-email-helpfix:
  send-email: remove stray characters from usage
</content>
</entry>
<entry>
<title>send-email: avoid duplicate specification warnings</title>
<updated>2023-11-16T22:26:34Z</updated>
<author>
<name>Todd Zullinger</name>
<email>tmz@pobox.com</email>
</author>
<published>2023-11-16T19:30:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=6ff658cc78f36baa74c0f25314b0043a8f4b4fc6'/>
<id>urn:sha1:6ff658cc78f36baa74c0f25314b0043a8f4b4fc6</id>
<content type='text'>
A warning is issued for options which are specified more than once
beginning with perl-Getopt-Long &gt;= 2.55.  In addition to causing users
to see warnings, this results in test failures which compare the output.
An example, from t9001-send-email.37:

  | +++ diff -u expect actual
  | --- expect      2023-11-14 10:38:23.854346488 +0000
  | +++ actual      2023-11-14 10:38:23.848346466 +0000
  | @@ -1,2 +1,7 @@
  | +Duplicate specification "no-chain-reply-to" for option "no-chain-reply-to"
  | +Duplicate specification "to-cover|to-cover!" for option "to-cover"
  | +Duplicate specification "cc-cover|cc-cover!" for option "cc-cover"
  | +Duplicate specification "no-thread" for option "no-thread"
  | +Duplicate specification "no-to-cover" for option "no-to-cover"
  |  fatal: longline.patch:35 is longer than 998 characters
  |  warning: no patches were sent
  | error: last command exited with $?=1
  | not ok 37 - reject long lines

Remove the duplicate option specs.  These are primarily the explicit
'--no-' prefix opts which were added in f471494303 (git-send-email.perl:
support no- prefix with older GetOptions, 2015-01-30).  This was done
specifically to support perl-5.8.0 which includes Getopt::Long 2.32[1].

Getopt::Long 2.33 added support for the '--no-' prefix natively by
appending '!' to the option specification string, which was included in
perl-5.8.1 and is not present in perl-5.8.0.  The previous commit bumped
the minimum supported Perl version to 5.8.1 so we no longer need to
provide the '--no-' variants for negatable options manually.

Teach `--git-completion-helper` to output the '--no-' options.  They are
not included in the options hash and would otherwise be lost.

Signed-off-by: Todd Zullinger &lt;tmz@pobox.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>perl: bump the required Perl version to 5.8.1 from 5.8.0</title>
<updated>2023-11-16T22:26:32Z</updated>
<author>
<name>Todd Zullinger</name>
<email>tmz@pobox.com</email>
</author>
<published>2023-11-16T19:30:10Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d13a73e383076636534e10ba799af0c9a2b85357'/>
<id>urn:sha1:d13a73e383076636534e10ba799af0c9a2b85357</id>
<content type='text'>
The following commit will make use of a Getopt::Long feature which is
only present in Perl &gt;= 5.8.1.  Document that as the minimum version we
support.

Many of our Perl scripts will continue to run with 5.8.0 but this change
allows us to adjust them as needed without breaking any promises to our
users.

The Perl requirement was last changed in d48b284183 (perl: bump the
required Perl version to 5.8 from 5.6.[21], 2010-09-24).  At that time,
5.8.0 was 8 years old.  It is now over 21 years old.

Signed-off-by: Todd Zullinger &lt;tmz@pobox.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>send-email: remove stray characters from usage</title>
<updated>2023-11-16T05:00:34Z</updated>
<author>
<name>Todd Zullinger</name>
<email>tmz@pobox.com</email>
</author>
<published>2023-11-15T17:39:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=46edab516bf04c190cb2e100419dee817d3f33f6'/>
<id>urn:sha1:46edab516bf04c190cb2e100419dee817d3f33f6</id>
<content type='text'>
A few stray single quotes crept into the usage string in a2ce608244
(send-email docs: add format-patch options, 2021-10-25).  Remove them.

Signed-off-by: Todd Zullinger &lt;tmz@pobox.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'ms/send-email-validate-fix'</title>
<updated>2023-11-07T01:26:44Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2023-11-07T01:26:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=00f372e2a419266fc9a41cb7b7935c9217e05ca7'/>
<id>urn:sha1:00f372e2a419266fc9a41cb7b7935c9217e05ca7</id>
<content type='text'>
"git send-email" did not have certain pieces of data computed yet
when it tried to validate the outging messages and its recipient
addresses, which has been sorted out.

* ms/send-email-validate-fix:
  send-email: move validation code below process_address_list
</content>
</entry>
<entry>
<title>Merge branch 'jk/send-email-fix-addresses-from-composed-messages'</title>
<updated>2023-10-29T22:09:59Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2023-10-29T22:09:58Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=5006bfc1f5c4bf231d6ec9221d70b41a02d6e937'/>
<id>urn:sha1:5006bfc1f5c4bf231d6ec9221d70b41a02d6e937</id>
<content type='text'>
The codepath to handle recipient addresses `git send-email
--compose` learns from the user was completely broken, which has
been corrected.

* jk/send-email-fix-addresses-from-composed-messages:
  send-email: handle to/cc/bcc from --compose message
  Revert "send-email: extract email-parsing code into a subroutine"
  doc/send-email: mention handling of "reply-to" with --compose
</content>
</entry>
</feed>
