On Wed, 26 Apr 2006, Paul Mackerras wrote: > > I just pushed some changes to gitk which add a new feature, the > ability to have multiple "views" of a repository. Each view is a > subgraph of the full graph. At the moment the only subgraph that you > can specify is the subgraph containing the commits that affect a > specified set of files or directories. You can switch between views > quickly, and if the currently selected commit exists in the new view > when you switch views, it is selected in the new view. This gets close to something I wanted, but at the same time falls very short of it because the views are always shown completely disjoint. I've wanted for a long time to have a way to _highlight_ commits. That's actually very much a "view" thing, but it's a mode where you really see one view, but the commits that exist in another view have a different color (or have the commits that _don't_ exist in the other view be grayed out). I hope that your new "view" thing would support this notion too: instead of having to totally switch between view, it would be wonderful if you could have one "master view" and then use another view to "highlight". Also, I think revision information should be part of a view. For example, in the "highlight" case, I'd love to have the "main view" be the default "everything", and then have some way to _highlight_ the view that is defined by the revision pattern "v1.3.1.." 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. (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). Linus - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html