git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Mukund Sivaraman <muks@banu.com>
Cc: git@vger.kernel.org
Subject: Re: Including branch info in git format-patch
Date: Thu, 19 Jun 2008 16:28:43 -0400	[thread overview]
Message-ID: <20080619202843.GA6207@sigill.intra.peff.net> (raw)
In-Reply-To: <20080619154251.GA16475@jurassic>

On Thu, Jun 19, 2008 at 09:12:52PM +0530, Mukund Sivaraman wrote:

> 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?

No, there isn't a way to do it automatically. On this mailing list,
patches are assumed to be on top of "master" unless explicitly indicated
otherwise. And we usually just mention it manually.

You could potentially add a config option to put the branch name inside
the '[PATCH]' text. This text is generally stripped away before
applying, so it would still free up the receiver to apply on whatever
branch they wanted. I don't think it would make sense for git
development, since we typically use topic branches, so keeping it
configurable would make sense.

On the receiving end, the applying party could set up their MUA to split
patches based on the subject, and then apply them as appropriate (this
very much depends on their workflow for applying patches). You could
probably even do a pre-applypatch hook as a safety valve to make sure
things were being applied in the right place.

-Peff

  reply	other threads:[~2008-06-19 20:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 15:42 Including branch info in git format-patch Mukund Sivaraman
2008-06-19 20:28 ` Jeff King [this message]
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=20080619202843.GA6207@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=muks@banu.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).