Re: Unexpected behavior in git-rev-list
- From
Junio C Hamano <junkio@cox.net>
- Date
- Sep 21, 2005, 18:34 UTC
- Message-ID
- <7vfyryw9ra.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <Pine.LNX.4.58.0509211022180.2553@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> writes:
Show 9 quoted lines
> It might be best not being done by git-rev-list, but by a specialized > program. However, the advantage of doing it in git-rev-list is that then > things like "git log" and "gitk" would automatically take advantage of it, > ie you could say > > gitk v2.6.12.. drivers/char/ > > and it would show a "cut-down" revision tree that only contained the stuff > that changed anything in drivers/char/.
Wouldn't gitk get confused by the sparse set of commits your rev-list feeds it, when it tries to draw ancestry lines and find many commits missing in between them?
Ah, you told him to use 'rev-list --parents' and you can rewrite the list of parents there -- clever.