From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <junkio@cox.net>
Cc: "Santi Béjar" <sbejar@gmail.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [BUG] git-rev-list: --topo-order --boundary and --max-count
Date: Mon, 5 Mar 2007 09:05:51 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0703050901370.3998@woody.linux-foundation.org> (raw)
In-Reply-To: <7vlkicynwm.fsf@assigned-by-dhcp.cox.net>
On Mon, 5 Mar 2007, Junio C Hamano wrote:
>
> I think the code that does --boundary when the list is limited
> with --max-count is not quite right, even without topo-order.
Yeah. Sadly, this is a really irritating bug, becuase it means that you
cannot do
gitk -50
to see some random collection of 50 recent commits.
(And yes, I've wanted to do that - I know the commit is fairly recent, so
rather than write "gitk @{1.hour.ag}..", I'd rather just be lazy and say
"gitk -100" to get a smaller slider bar and easier to find the recent
ones).
I never cared enough to fix it, but it's a mis-feature. I agree that it's
probably not entirely trivial to fix.
Linus
next prev parent reply other threads:[~2007-03-05 17:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 10:02 [BUG] git-rev-list: --topo-order --boundary and --max-count Santi Béjar
2007-03-05 10:39 ` Junio C Hamano
2007-03-05 12:15 ` Junio C Hamano
2007-03-05 17:05 ` Linus Torvalds [this message]
2007-03-05 18:55 ` [PATCH] revision walker: Fix --boundary when limited Johannes Schindelin
2007-03-05 19:00 ` Johannes Schindelin
2007-03-05 19:39 ` Linus Torvalds
2007-03-05 19:57 ` Linus Torvalds
2007-03-05 21:10 ` Junio C Hamano
2007-03-06 1:12 ` Johannes Schindelin
2007-03-06 1:32 ` Junio C Hamano
2007-03-06 1:44 ` Johannes Schindelin
2007-03-06 1:58 ` Junio C Hamano
2007-03-05 23:17 ` Johannes Schindelin
2007-03-06 0:36 ` Junio C Hamano
2007-03-06 0:41 ` [PATCH 2/4] revision traversal: retire BOUNDARY_SHOW Junio C Hamano
2007-03-06 2:05 ` Johannes Schindelin
2007-03-06 2:17 ` Junio C Hamano
2007-03-06 2:23 ` SHOWN means shown Junio C Hamano
2007-03-06 2:29 ` [PATCH 2/4] revision traversal: retire BOUNDARY_SHOW Johannes Schindelin
2007-03-06 11:34 ` Junio C Hamano
2007-03-06 15:52 ` Johannes Schindelin
2007-03-06 0:41 ` [PATCH 3/4] git-bundle: various fixups Junio C Hamano
2007-03-06 2:13 ` Johannes Schindelin
2007-03-06 0:41 ` [PATCH 4/4] git-bundle: --list-prereqs Junio C Hamano
2007-03-05 21:10 ` [PATCH] revision walker: Fix --boundary when limited Junio C Hamano
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=Pine.LNX.4.64.0703050901370.3998@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=sbejar@gmail.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).