From: Markus Heidelberg <markus.heidelberg@web.de>
Date: Sun, 04 Jan 2009 18:01:18 GMT
Subject: Re: [PATCH next] git-cherry usage: correct nesting of commit-ish options
Message-ID: <200901041901.18801.markus.heidelberg@web.de>
In-Reply-To: <20090104173559.GG21154@genesis.frugalware.org>

Miklos Vajna, 04.01.2009:
> 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.