From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Re: Make new builtin cherry match documentation for "+" and "-"
Date: Thu, 26 Oct 2006 08:45:22 +0100 [thread overview]
Message-ID: <200610260845.23850.andyparkins@gmail.com> (raw)
In-Reply-To: <7vk62ob5mp.fsf@assigned-by-dhcp.cox.net>
On Wednesday 2006 October 25 19:41, Junio C Hamano wrote:
> > "+" and "-" don't match the documentation, where "+" means the patch /is/
> > in upstream, "-" means it isn't
>
> The documentation was utterly wrong. The comment at the
> beginning of git-cherry.sh was better but slightly wrong.
Seriously? In git-cherry output a "-" means that a patch is in? Seems
counter-intuitive to me.
Or is it meant to be analogous to a diff so "+" means "in order to make this
branch like the comparison branch you would have to /add/ this patch"?
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
next prev parent reply other threads:[~2006-10-26 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 14:49 (unknown) andyparkins
2006-10-25 18:41 ` (unknown) Junio C Hamano
2006-10-26 7:45 ` Andy Parkins [this message]
2006-10-26 8:22 ` Make new builtin cherry match documentation for "+" and "-" Junio C Hamano
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=200610260845.23850.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
/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).