From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org, "Randal L. Schwartz" <merlyn@stonehenge.com>
Subject: Re: git-log to go forward instead of reverse?
Date: Mon, 10 Jul 2006 14:45:11 -0700 [thread overview]
Message-ID: <7vpsgd9lso.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.64.0607101304210.5623@g5.osdl.org
Linus Torvalds <torvalds@osdl.org> writes:
> And if you didn't know about "git shortlog" already, I personally actually
> find it easier to read
>
> git log --no-merges ORIG_HEAD.. | git shortlog
>
> which orders things by author instead.
Yes, and you can even have '-p' between git and shortlog in the
latter command if you do want the pager ;-).
BTW, when I prepare the "What's in" messages, I often find it
more useful to have a brother of short-log command that does not
group by author but group by topic branch the commits came from.
Currently I prepare the categorized list by hand, reviewing each
commit in "master..next" shortlog output. While I do not mind
it too much since that is a good way to remind myself what are
still cooking, it would be nice to have to a command that takes:
- which branch the output is relative to (defaults
to "master");
- list of branches that are "topics";
- which branch the parts of topics have been merged to
(optional -- I'd use "next" for my use).
and for each topic:
- see if the topic branches off from another topic (for
example, the merge-tree topic branches off from the
xdiff-common topic like [*1*]); if so, state that and
use that branch point instead of "master" in the next
step;
- list commits that have not made "master" yet;
optionally, when "next" is given, limit the output
only to the ones that have made "next" already.
[Footnote]
*1*
$ git show-branch --topics master lt/xdiff-common lt/merge-tree
* [master] git-rev-list: add documentation for --parents, --no-merges
! [lt/xdiff-common] xdiff: generate "anti-diffs" aka what is common...
! [lt/merge-tree] Improved three-way blob merging code
---
+ [lt/merge-tree] Improved three-way blob merging code
+ [lt/merge-tree^] Prepare "git-merge-tree" for future work
++ [lt/xdiff-common] xdiff: generate "anti-diffs" aka what is common...
*++ [master~67] checkout -m: fix read-tree invocation
next prev parent reply other threads:[~2006-07-10 21:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 18:42 git-log to go forward instead of reverse? Randal L. Schwartz
2006-07-10 19:01 ` Linus Torvalds
2006-07-10 19:06 ` Randal L. Schwartz
2006-07-10 19:20 ` Linus Torvalds
2006-07-10 19:25 ` Randal L. Schwartz
2006-07-10 20:09 ` Linus Torvalds
2006-07-10 20:16 ` Randal L. Schwartz
2006-07-10 21:45 ` Junio C Hamano [this message]
2006-07-10 20:26 ` Junio C Hamano
2006-07-10 20:31 ` Randal L. Schwartz
2006-07-10 19:26 ` Linus Torvalds
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=7vpsgd9lso.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=torvalds@osdl.org \
/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).