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
Miklos Vajna <vmiklos@frugalware.org>
Date
Jan 4, 2009, 22:47 UTC
Message-ID
<20090104224727.GJ21154@genesis.frugalware.org>
In-Reply-To
<200901041901.18801.markus.heidelberg@web.de>
On Sun, Jan 04, 2009 at 07:01:18PM +0100, Markus Heidelberg <markus.heidelberg@web.de> wrote:
Show 6 quoted lines
> > 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.

Ouch, then sorry for the misinformation. (Especially that it turns out Junio added that line in 45d2b286.)

Previous: Markus Heidelberg
Message 5 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.