git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[ISSUE] git send-email sends wrong patches and non-provided CC (probably bug)

From
Imran M Yousuf <imyousuf@gmail.com>
Date
Mar 6, 2008, 09:11 UTC
Message-ID
<7bfdc29a0803060111vc98ef42q96c3ce343fef0859@mail.gmail.com>
Hi,

Firstly sorry to gitster as he probably has received 10 redundant emails from me of my own patch, which I sent for test purpose before sending to the mailing list. In this process actually I found 2 issues:

1. git send-email sends CC to gitster though his email is not mentioned.
2. I wanted to send patches from a folder containing 3 patches
generated with 'git format-patch -n -o /output/dir/ -M -B origin'
command. When I use git send-email it rather sends 5 email; 3 for
PATCH 3/3 with same subject but different body. I later generated them
without -n option and sent to the mailing list and that was sent
correctly. Unfortunately gitster has 13 emails of the same content out
of 10 are outcomes of the bug. I am providing their message id so that
he can have a look at them:
Message-Id: <1204793490-20160-5-git-send-email-imyousuf@gmail.com>
Message-Id: <1204788919-23615-3-git-send-email-imyousuf@gmail.com>

If someone else wants to have a look at the problem I can also email it to him :).

-- 
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: imran@smartitengineering.com
Mobile: +880-1711402557
Next: Junio C Hamano
Message 1 of 4 in “[ISSUE] git send-email sends wrong patches and non-provided CC (probably bug)”
  1. Imran M YousufMar 6, 2008
  2. Junio C HamanoMar 6, 2008
  3. Imran M YousufMar 6, 2008
  4. Junio C HamanoMar 8, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.