From: Jakub Narebski <jnareb@gmail.com>
To: Sergei Organov <osv@javad.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] user-manual: Talk about tracking third-party snapshots
Date: Tue, 13 Nov 2007 16:38:50 +0100 [thread overview]
Message-ID: <200711131638.50437.jnareb@gmail.com> (raw)
In-Reply-To: <87zlxi88op.fsf@osv.gnss.ru>
Sergei Organov wrote:
> Jakub Narebski <jnareb@gmail.com> 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
next prev parent reply other threads:[~2007-11-13 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 12:29 [PATCH] user-manual: Talk about tracking third-party snapshots Michael Smith
2007-11-13 14:07 ` Jakub Narebski
2007-11-13 15:30 ` Sergei Organov
2007-11-13 15:38 ` Jakub Narebski [this message]
2007-11-17 16:45 ` Jan Hudec
2007-11-17 18:18 ` Jakub Narebski
2007-11-17 19:18 ` Jan Hudec
2007-11-17 19:54 ` Jakub Narebski
2007-11-13 19:25 ` Junio C Hamano
2007-11-13 21:37 ` Michael Smith
2007-11-19 1:17 ` J. Bruce Fields
2007-11-19 0:48 ` J. Bruce Fields
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=200711131638.50437.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=osv@javad.com \
/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).