From: Mukund Sivaraman <muks@banu.com>
To: git@vger.kernel.org
Subject: Including branch info in git format-patch
Date: Thu, 19 Jun 2008 21:12:52 +0530 [thread overview]
Message-ID: <20080619154251.GA16475@jurassic> (raw)
Hi all
We have two public branches on the tinyproxy project[1]: master and 1.6.
We send patches to the mailing list to get them reviewed before they are
applied and pushed to the public repo.
When i use "git format-patch", it doesn't seem to include the branch (or
remote) name in the email it creates. So a reader of this mail may not
know what branch to apply it on to test it. Aside from adding in branch
information manually in the body of the message, is there any other
existing way to get git format-patch to include it?
Apologies in advance if this is a stupid question.
Mukund
Refs:
1. http://git.banu.com/?p=tinyproxy;a=summary
next reply other threads:[~2008-06-19 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 15:42 Mukund Sivaraman [this message]
2008-06-19 20:28 ` Including branch info in git format-patch Jeff King
2008-06-19 20:54 ` Junio C Hamano
2008-06-19 21:06 ` Jeff King
2008-06-19 21:08 ` Jeff King
2008-06-19 21:15 ` Sverre Rabbelier
2008-06-19 21:26 ` Mukund Sivaraman
2008-06-19 21:41 ` Junio C Hamano
2008-06-19 21:55 ` Mukund Sivaraman
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=20080619154251.GA16475@jurassic \
--to=muks@banu.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).