Re: [PATCH] user-manual: Talk about tracking third-party snapshots

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sergei Organov wrote:
> Jakub Narebski <jnareb@xxxxxxxxx> writes:
> 
>> Michael Smith wrote:
>>
>>> +You can use the gitlink:git-cherry[1] command to display the commit
>>> +IDs that are only present on your local branch, or only on the remote
>>> +branch, respectively:
>>
>> I think git-cherry is deprecated in favor of "git log --left-right" (with
>> appropriate format, for example '--abbrev-commit --pretty=oneline')
>>
>> BTW. that means that git-cherry can be removed from git-help output,
>> I think.
> 
> And from core-tutorial.txt:1567:
> 
> 4. Use `git cherry origin` to see which ones of your patches
>    were accepted, and/or use `git rebase origin` to port your
>    unmerged changes forward to the updated upstream.
> 
> ???

On one hand, core-tutorial is old documentation, dating before
--left-right option to git-log.

On the other hand I have forgot that git-cherry does more throghout
checking if patch was accepted upstream (by checking changeset).


Sorry for the noise...
-- 
Jakub Narebski
Poland
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux