From: Miklos Vajna <vmiklos@frugalware.org>
To: Markus Heidelberg <markus.heidelberg@web.de>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH next] git-cherry usage: correct nesting of commit-ish options
Date: Sun, 4 Jan 2009 23:47:27 +0100 [thread overview]
Message-ID: <20090104224727.GJ21154@genesis.frugalware.org> (raw)
In-Reply-To: <200901041901.18801.markus.heidelberg@web.de>
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
On Sun, Jan 04, 2009 at 07:01:18PM +0100, Markus Heidelberg <markus.heidelberg@web.de> wrote:
> > 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.)
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-01-04 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 16:11 [PATCH next] git-cherry usage: correct nesting of commit-ish options Markus Heidelberg
2009-01-04 16:16 ` Markus Heidelberg
2009-01-04 17:35 ` Miklos Vajna
2009-01-04 18:01 ` Markus Heidelberg
2009-01-04 22:47 ` Miklos Vajna [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090104224727.GJ21154@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=markus.heidelberg@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).