git-cherry(1)'s description section has never really managed to
explain to me what the command does. It contains too much explanation
of the algorithm instead of simply saying what goals it achieves, and
too much terminology that we otherwise do not use (fork-point instead
of merge-base).
Try a
On Thu, Nov 21, 2013 at 12:30:56PM +0100, Thomas Rast wrote:
git-cherry(1)'s description section has never really managed to
explain to me what the command does. It contains too much explanation
of the algorithm instead of simply saying what goals it achieves, and
too much terminology that
Thomas Rast t...@thomasrast.ch writes:
Junio C Hamano gits...@pobox.com writes:
OPTIONS
---
-v::
- Verbose.
+ Verbose. Currently shows the commit subjects next to their
+ SHA1.
Whenever I see Currently, it makes me wonder why does it need to
say that? Is there a plan to
Thomas Rast t...@thomasrast.ch writes:
NAME
-git-cherry - Find commits not merged upstream
+git-cherry - Find commits not applied in upstream
Good.
+Determine whether there are commits in `head..upstream` that are
+equivalent to those in the range `limit..head`.
+The
Junio C Hamano gits...@pobox.com writes:
OPTIONS
---
-v::
-Verbose.
+Verbose. Currently shows the commit subjects next to their
+SHA1.
Whenever I see Currently, it makes me wonder why does it need to
say that? Is there a plan to change it soon, and if so where is the
Jeff King p...@peff.net writes:
On Thu, Nov 21, 2013 at 12:30:56PM +0100, Thomas Rast wrote:
+Later, you can whether your changes have been applied by saying (still
+on `topic`):
s/can/ see/ ?
+Note that this uses , and assumes that
+`core.autosetupmerge` is enabled (the default).
I
6 matches
Mail list logo
