As suggested by Documentation/SubmittingPatches Hi, this is my first patch.\n I basically stumbled on the same issue mentioned here: https://public-inbox.org/git/xmqqzim1pp4m.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx/ This patch implements two new command line options for `git log`: `--decorate-refs=<pattern>` and `--decorate-refs-exlcude=<pattern>` Both options accept a glob pattern which determines what decorations commits receive. At first I considered adding '--trim-decoration', that would filter refs based on values passed to '--branches=' '--remotes=' '--tags=' and '--exclude='. After reading the email, I think it's better to have those two behaviours decoupled. I also had plans to add: (Not sure if others deserve having their own command) --decorate-branches= --decorate-remotes= --decorate-tags= But was not sure if a 'niche' function like this is worth 5+ command line options. I personally find that those two are enough. --- Rafael Ascensão Rafael Ascensão (2): refs: extract function to normalize partial refs log: add option to choose which refs to decorate Documentation/git-log.txt | 12 ++++++ builtin/log.c | 10 ++++- log-tree.c | 37 ++++++++++++++--- log-tree.h | 6 ++- pretty.c | 4 +- refs.c | 34 +++++++++------- refs.h | 16 ++++++++ revision.c | 2 +- t/t4202-log.sh | 101 ++++++++++++++++++++++++++++++++++++++++++++++ 9 files changed, 198 insertions(+), 24 deletions(-) -- 2.15.0
