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

Re: [PATCH next] git-cherry usage: correct nesting of commit-ish options

From
Markus Heidelberg <markus.heidelberg@web.de>
Date
Jan 4, 2009, 16:16 UTC
Message-ID
<200901041716.00673.markus.heidelberg@web.de>
In-Reply-To
<200901041711.23026.markus.heidelberg@web.de>
Markus Heidelberg, 04.01.2009:
Show 8 quoted lines
> 
> Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>
> ---
> 
> What is the preferred way to say the patch is against next? In the
> subject like this?
> Another question: should this patch be split up into two, one for
> maint/master and another for next?

For the second patch against next I meant it being based on origin/next that already includes the extracted patch for maint/master.

Previous: Markus HeidelbergNext: Miklos Vajna
Message 2 of 5 in “git-cherry usage: correct nesting of commit-ish options”
  1. git-cherry usage: correct nesting of commit-ish optionsMarkus Heidelberg, Jan 4, 2009
  2. Markus HeidelbergJan 4, 2009
  3. Miklos VajnaJan 4, 2009
  4. Markus HeidelbergJan 4, 2009
  5. Miklos VajnaJan 4, 2009

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.