Package: git-email
Version: 1:1.7.1-1.1
Severity: normal

It is very easy to shoot yourself into the respective foot when
combining git format-patch with git send-email:

ametz...@argenau:/tmp/WMAKER/wmaker-crm.git$ git format-patch -o /tmp/gittest 
-M --to=ametz...@downhill.at.eu.org --thread=shallow 
8b6f37d4bb5245d5debcf3aad30e9d98cceb3db9
/tmp/gittest/0001-actually-add-bug-number.patch
/tmp/gittest/0002-SelectWindowsMouseButton-MouseLeftButtonAction.patch
ametz...@argenau:/tmp/WMAKER/wmaker-crm.git$ git send-email 
--to=ametz...@downhill.at.eu.org --smtp-server=localhost --suppress-cc=self 
/tmp/gittest/
[...]

With these options git send-email sends out mails that have:
* Two To: headers
* Two In-Reply-To: headers
* Two References: headers

In the given example all duplicate headers are identical, but that is
just the specific example, git send-email will happily add conflicting
To, In-Reply-To and References headers.

git send-email should check for existing headers in the input mbox
files and replace them (or at least rename them, e.g.
X-Original-To: ...) instead of blindly appending new ones.

Bug report written on lenny, I originally experienced the issue with
the backport 1:1.7.1-1.1~bpo50+1 but have verified that the package in
sid behaves the same way.

cu andreas

-- System Information:
Debian Release: 5.0.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages git-email depends on:
ii  git                  1:1.7.1-1.1 fast, scalable, distributed revisi

Versions of packages git-email recommends:
pn  libauthen-sasl-perl           <none>     (no description available)
ii  libemail-valid-perl           0.179-2    Check validity of Internet email a
pn  libnet-smtp-ssl-perl          <none>     (no description available)

Versions of packages git-email suggests:
pn  git-doc                       <none>     (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to