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

Re: Including branch info in git format-patch

From
MSMukund Sivaraman <muks@banu.com>
Date
Jun 19, 2008, 21:55 UTC
Message-ID
<20080619215512.GA29693@jurassic>
In-Reply-To
<7vod5xrtjx.fsf@gitster.siamese.dyndns.org>
On Thu, Jun 19, 2008 at 02:41:54PM -0700, Junio C Hamano wrote:
Show 7 quoted lines
> > My problem is that I can't send a patch out to the list for other
> > developers to try, without some annotation for them, of which branch to
> > try it on.
> 
> So what's wrong telling that when you send out the patch, between the time
> you run format-patch and send-email?
>

I had asked if there was some way the remote branch name could automatically be inserted by git format-patch, instead of manually adding it in the patch message or in a cover letter. What Jeff suggested seems good to me (of using --subject-prefix) as that is removed automatically when the patch is applied by git am.

		Mukund
Previous: Junio C Hamano
Message 9 of 9 in “Including branch info in git format-patch”
  1. Mukund SivaramanJun 19, 2008
  2. Jeff KingJun 19, 2008
  3. Junio C HamanoJun 19, 2008
  4. Jeff KingJun 19, 2008
  5. Jeff KingJun 19, 2008
  6. Sverre RabbelierJun 19, 2008
  7. Mukund SivaramanJun 19, 2008
  8. Junio C HamanoJun 19, 2008
  9. Mukund SivaramanJun 19, 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.