git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Imran M Yousuf" <imyousuf@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Cc: "Junio C Hamano" <gitster@pobox.com>
Subject: [ISSUE] git send-email sends wrong patches and non-provided CC (probably bug)
Date: Thu, 6 Mar 2008 15:11:19 +0600	[thread overview]
Message-ID: <7bfdc29a0803060111vc98ef42q96c3ce343fef0859@mail.gmail.com> (raw)

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

             reply	other threads:[~2008-03-06  9:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06  9:11 Imran M Yousuf [this message]
2008-03-06 10:19 ` [ISSUE] git send-email sends wrong patches and non-provided CC (probably bug) Junio C Hamano
2008-03-06 11:19   ` Imran M Yousuf
2008-03-08  5:14     ` Junio C Hamano

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=7bfdc29a0803060111vc98ef42q96c3ce343fef0859@mail.gmail.com \
    --to=imyousuf@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).