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, 18:01 UTC
Message-ID
<200901041901.18801.markus.heidelberg@web.de>
In-Reply-To
<20090104173559.GG21154@genesis.frugalware.org>
Miklos Vajna, 04.01.2009:
Show 5 quoted lines
> On Sun, Jan 04, 2009 at 05:11:22PM +0100, Markus Heidelberg <markus.heidelberg@web.de> wrote:
> > Another question: should this patch be split up into two, one for
> > maint/master and another for next?
> 
> AFAIK sending patches against next is not preferred at all.
>From Documentation/SubmittingPatches:
    If you are preparing a work based on "next" branch,
    that is fine, but please mark it as such.

I guess the only reason is a required dependency not available in 'master'.

> You should
> send your patches against master, or - if you have a strong reason - on
> top of a given topic branch.

This patch depends on a commit in 'next'. But right, I could have mentioned that it's against 'mh/cherry-default' as Junio suggested a few days ago.

Previous: Miklos VajnaNext: Miklos Vajna
Message 4 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.