From: "Carlos Martín Nieto" <cmn@elego.de>
To: Yann Dirson <dirson@bertin.fr>
Cc: git list <git@vger.kernel.org>
Subject: Re: [BUG] cherry-pick ignores some arguments
Date: Fri, 15 Jun 2012 16:39:18 +0200 [thread overview]
Message-ID: <1339771158.4625.59.camel@beez.lab.cmartin.tk> (raw)
In-Reply-To: <1339765943.4625.57.camel@beez.lab.cmartin.tk>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
On Fri, 2012-06-15 at 15:12 +0200, Carlos Martín Nieto wrote:
> The typical cherry-pick usage is for a few select commits out of a
> different branch. The manpage itself only started explaining the ranges
> in 2010 and they may be more of a side-effect than a conscious design
> decision. But that's neither here nor there.
Disregard this part. I just found the patches. For some reason I thought
that the capability was there much earlier.
cmn
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2012-06-15 14:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 9:44 [BUG] cherry-pick ignores some arguments Yann Dirson
2012-06-14 16:29 ` Carlos Martín Nieto
2012-06-15 7:14 ` Yann Dirson
2012-06-15 13:12 ` Carlos Martín Nieto
2012-06-15 14:33 ` [PATCH 1/2] Documentation: --no-walk is no-op if range is specified Carlos Martín Nieto
2012-06-15 14:33 ` [PATCH 2/2] git-cherry-pick.txt: make clearer when revision walking gets activated Carlos Martín Nieto
2012-06-15 17:52 ` Junio C Hamano
2012-06-15 17:37 ` [PATCH 1/2] Documentation: --no-walk is no-op if range is specified Junio C Hamano
2012-06-15 14:39 ` Carlos Martín Nieto [this message]
2012-06-15 15:06 ` [BUG] cherry-pick ignores some arguments Junio C Hamano
2012-06-15 15:03 ` 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=1339771158.4625.59.camel@beez.lab.cmartin.tk \
--to=cmn@elego.de \
--cc=dirson@bertin.fr \
--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).