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

Re: [PATCH] Use commit template when cherry picking

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 11, 2008, 12:10 UTC
Message-ID
<alpine.LSU.1.00.0801111208020.31053@racer.site>
In-Reply-To
<20080111074505.GC14022@plexity.net>
Hi,
On Thu, 10 Jan 2008, Deepak Saxena wrote:
Show 5 quoted lines
> We are using git to manage our kernel tree and we often cherry-pick 
> patches from upstream and while we want to save the original commit 
> message, we also want to apply our default commit header to the log. If 
> this patch is not the ideal solution, please let me know how I should go 
> about this.

I would do a combination of "cherry-pick -n", "cat-file commit <commit> | sed '1,/^$/d'" and "commit -F" or "commit -f".

You can make this an alias, too.

Hth, Dscho

Previous: Deepak SaxenaNext: Junio C Hamano
Message 2 of 4 in “Use commit template when cherry picking”
  1. Use commit template when cherry pickingDeepak Saxena, Jan 11, 2008
  2. Johannes SchindelinJan 11, 2008
  3. Junio C HamanoJan 11, 2008
  4. Johannes SchindelinJan 11, 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.