2009/2/15 Junio C Hamano <gitster@xxxxxxxxx>: > Many options you add here are useful for git-log and not present in its > completion, but as you point out not all git-log options necessarily make > sense for gitk. I think it would make sense to introduce an extra > variable $__git_log_basic_options that holds the basic ones that can be in > both, and add the ones that are specific to gitk or git-log in their own > completion functions. I suspect gitk's addition will be nil, while > git-log would add --graph, --walk-reflogs and --no-merges to the basic > set. I sometimes use the --no-merges with gitk, normally within a range (the last 'next' update or so). Santi -- To unsubscribe from this list: 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
