From: Frank Lichtenheld <frank@lichtenheld.de>
To: "J. Bruce Fields" <bfields@citi.umich.edu>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 08/10] user-manual: add a "counting commits" example
Date: Mon, 14 May 2007 17:51:11 +0200 [thread overview]
Message-ID: <20070514155111.GE5272@planck.djpig.de> (raw)
On Mon, May 14, 2007 at 11:21:27AM -0400, J. Bruce Fields wrote:
> +Suppose you want to know how many commits you've made on "mybranch"
> +since it diverged from "origin":
> +
> +-------------------------------------------------
> +$ git log --pretty=oneline origin..maint | wc -l
> +-------------------------------------------------
Shouldn't that be mybranch instead of maint?
> +Alternatively you may often see this sort of thing done with the
> +lower-level command gitlink:git-rev-list[1], which just lists the SHA1's
> +of all the given commits:
> +
> +-------------------------------------------------
> +$ git rev-list origin..maint | wc -l
> +-------------------------------------------------
Same here.
Gruesse,
--
Frank Lichtenheld <frank@lichtenheld.de>
www: http://www.djpig.de/
next reply other threads:[~2007-05-14 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 15:51 Frank Lichtenheld [this message]
2007-05-14 16:03 ` [PATCH 08/10] user-manual: add a "counting commits" example J. Bruce Fields
2007-05-14 16:05 ` [PATCH] user-manual: fix branch names in examples J. Bruce Fields
2007-05-14 21:31 ` Junio C Hamano
2007-05-14 21:38 ` J. Bruce Fields
[not found] <11791560893572-git-send-email->
[not found] ` <1179156089759-git-send-email->
[not found] ` <11791560893022-git-send-email->
[not found] ` <11791560891179-git-send-email->
[not found] ` <1179156089470-git-send-email->
[not found] ` <11791560892667-git-send-email->
[not found] ` <11791560901-git-send-email->
2007-05-14 15:21 ` [PATCH 08/10] user-manual: add a "counting commits" example 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=20070514155111.GE5272@planck.djpig.de \
--to=frank@lichtenheld.de \
--cc=bfields@citi.umich.edu \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).