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

Re: git-format-patch builtin isn't using git-cherry?

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 23, 2006, 12:33 UTC
Message-ID
<Pine.LNX.4.63.0606231431420.29667@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<20060623152321.2c20e9f8.tihirvon@gmail.com>
Hi,
On Fri, 23 Jun 2006, Timo Hirvonen wrote:
Show 8 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> 
> > Basically, it will involve the following recipe:
> > 
> > 	- add a DIFF_FORMAT_PATCH_ID
> 
> Please don't add any DIFF_FORMAT_*.  I'm cleaning the diff output code
> and replacing diff_options.output_format with one-bit flags.

Okay. For the purposes of git-format-patch, this is not needed anyway, but rather a function which takes two tree objects and returns the patch id. When you are finished it should be easy to add this as a display format.

Ciao, Dscho

Previous: Timo HirvonenNext: Johannes Schindelin
Message 4 of 5 in “git-format-patch builtin isn't using git-cherry?”
  1. Martin LanghoffJun 23, 2006
  2. Johannes SchindelinJun 23, 2006
  3. Timo HirvonenJun 23, 2006
  4. Johannes SchindelinJun 23, 2006
  5. diff: add diff_flush_patch_id()Johannes Schindelin, Jun 23, 2006

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.