From: "Imran M Yousuf" <imyousuf@gmail.com>
To: git@vger.kernel.org
Subject: Sending a patch using git-send-email
Date: Wed, 9 Jan 2008 09:29:53 +0600 [thread overview]
Message-ID: <7bfdc29a0801081929i5b8c9cc6i9a8b6aeb38f22027@mail.gmail.com> (raw)
Hi All,
I am using
git-send-email --to imyousuf@gmail.com --cc
imran.yousuf@smartitengineering.com --from imyousuf@gmail.com
~/Desktop/0001-Signed-off-by-Imran-M-Yousuf-imran-smartitengineer.patch
to send a patch, now if I use --subject "test subject" --compose I get
2 emails one with subject "test subject" and body I gave in the
composer and another with patch subject and the patch as body. Is
there a way to combine them?
git-send-email --to imyousuf@gmail.com --subject "Simplified action
invocation in git submodule" --from imyousuf@gmail.com --compose
~/Desktop/0001-Signed-off-by-Imran-M-Yousuf-imran-smartitengineer.patch
was the command I was using for subject and compose.
I would be grateful if you would be kind enough to help me as I have
several patches pending to be sent for this.
Thank you & Best regards,
--
Imran M Yousuf
reply other threads:[~2008-01-09 3:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7bfdc29a0801081929i5b8c9cc6i9a8b6aeb38f22027@mail.gmail.com \
--to=imyousuf@gmail.com \
--cc=git@vger.kernel.org \
/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).