From: Linus Torvalds <torvalds@osdl.org>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: Re: new gitk feature
Date: Thu, 27 Apr 2006 22:11:14 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0604272209060.3701@g5.osdl.org> (raw)
In-Reply-To: <17489.22838.502099.575465@cargo.ozlabs.ibm.com>
On Fri, 28 Apr 2006, Paul Mackerras wrote:
> Linus Torvalds writes:
> > Any possibility of something light that? I'd _love_ to be able to see the
> > whole tree, but with things that touch certain files or things that are
> > newer highlighted.
>
> That should be quite doable. How about I show the commits that are in
> the highlight view in bold? That won't conflict with the existing
> yellow background for commits that match the find criteria.
Bold sounds good to me.
> > (Btw, the "revision information" is also cool things like "--unpacked". I
> > actually use "gitk --unpacked" every once in a while, just because it's
> > such a cool way to say "show me everything I've added since I packed the
> > repo last).
>
> OK, I didn't know about --unpacked. :) I plan to add stuff to the
> view definition window to allow you to select commits to
> include/exclude by reachability from given commits (by head/tag/ID)
> and when I do I can add a way to say --unpacked too.
It's more of a gimmick, but I find myself using it occasionally just to
decide whether it's time to repack. It falls out automatically - not
because I thought I'd ever want it, but because the --unpacked semantics
for git-rev-list are what incremental packing needed.
(Of course, sane people probably just do "git count-objects" to decide to
repack).
Linus
prev parent reply other threads:[~2006-04-28 5:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 10:59 new gitk feature Paul Mackerras
2006-04-26 13:57 ` Jan-Benedict Glaw
2006-04-26 15:09 ` Linus Torvalds
2006-04-27 23:52 ` Paul Mackerras
2006-04-28 5:11 ` Linus Torvalds [this message]
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.0604272209060.3701@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=paulus@samba.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).