From: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Add link to git-cherry(1) in git-cherry-pick(1)
Date: Sat, 5 Mar 2011 20:26:25 +0100 [thread overview]
Message-ID: <AANLkTikumH9gSMtJO2FR=oGPh4NP-xEYYxdcv8heH9J1@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=QZhtByUe5h5w1MFrQ703MsWpoWHZcxvFsvNZk@mail.gmail.com>
Ignore that - I didn't understand how the 'cherry' works.
Anyway, two questions:
1. is there a reason why git-cherry is separate command and not part
of git-branch?
2. is there a way to make gitk show cherry-picks (or plans for implementing it)?
On Sat, Mar 5, 2011 at 8:12 PM, Piotr Krukowiecki
<piotr.krukowiecki@gmail.com> wrote:
> Hm now I started to wonder: is git cherry the same as git branch --contains?
>
> On Sat, Mar 5, 2011 at 8:09 PM, Piotr Krukowiecki
> <piotr.krukowiecki@gmail.com> wrote:
>>
>> Signed-off-by: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
>> ---
>> Documentation/git-cherry-pick.txt | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/Documentation/git-cherry-pick.txt b/Documentation/git-cherry-pick.txt
>> index 749d68a..c078cc9 100644
>> --- a/Documentation/git-cherry-pick.txt
>> +++ b/Documentation/git-cherry-pick.txt
>> @@ -162,7 +162,7 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
>>
>> SEE ALSO
>> --------
>> -linkgit:git-revert[1]
>> +linkgit:git-revert[1], linkgit:git-cherry[1]
>>
>> GIT
>> ---
>> --
>> 1.7.4.1.179.gb9a20
>>
>> --
>> Piotr Krukowiecki
>>
>
>
>
> --
> Piotrek
>
--
Piotrek
prev parent reply other threads:[~2011-03-05 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 19:09 [PATCH] Add link to git-cherry(1) in git-cherry-pick(1) Piotr Krukowiecki
2011-03-05 19:12 ` Piotr Krukowiecki
2011-03-05 19:26 ` Piotr Krukowiecki [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='AANLkTikumH9gSMtJO2FR=oGPh4NP-xEYYxdcv8heH9J1@mail.gmail.com' \
--to=piotr.krukowiecki@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).