* [PATCH] Add link to git-cherry(1) in git-cherry-pick(1)
@ 2011-03-05 19:09 Piotr Krukowiecki
2011-03-05 19:12 ` Piotr Krukowiecki
0 siblings, 1 reply; 3+ messages in thread
From: Piotr Krukowiecki @ 2011-03-05 19:09 UTC (permalink / raw)
To: git
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
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] Add link to git-cherry(1) in git-cherry-pick(1)
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
0 siblings, 1 reply; 3+ messages in thread
From: Piotr Krukowiecki @ 2011-03-05 19:12 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] Add link to git-cherry(1) in git-cherry-pick(1)
2011-03-05 19:12 ` Piotr Krukowiecki
@ 2011-03-05 19:26 ` Piotr Krukowiecki
0 siblings, 0 replies; 3+ messages in thread
From: Piotr Krukowiecki @ 2011-03-05 19:26 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-03-05 19:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).