also sprach Jonathan Nieder <jrnie...@gmail.com> [2011.08.02.2227 +0200]: > Does "gitk --branches --tags --remotes" do the trick? If not, what do > you think a good UI would look like?
Since notes are also shown in the commit message display of gitk (cf. #636226), having their DAG show up seems redundant. In addition, the notes commits are an implementation detail. Therefore, I tend to think that refs/notes/* or at least refs/notes/commit should /not/ show up unless /explicitly/ selected, e.g. with --notes… > (Example: a new option used like "gitk --all --exclude=notes", with a > configuration variable "[log] excluderef" to determine a default set > of excluded refs. Probably needs some tweak to prevent confusion when > commands like "gitk <name of a notes ref>" or "gitk > --glob=refs/notes/*" show nothing.) … or unless a ref within that DAG is specified explicitly. My original suggestion was not to special-case notes, but to provide a generic exclude mechanism. Other candidates I can think of are refs/heads/pristine-tar (probably a Debian-only configuration default) and refs/top-bases/* (arguably a default, since most people do not use TopGit (yet)). I think a configuration option list of refs to exclude, which is set to refs/notes/* by default (adding refs/heads/pristine-tar on Debian) would do. Since gitk only shows commits reachable by visible refs, this would do, and it would provide everyone with the ability to further adapt gitk to their own preference. Thank you for your consideration! -- .''`. martin f. krafft <madduck@d.o> Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduck http://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "first get your facts; then you can distort them at your leisure." -- mark twain
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
