{"thread":{"id":"49673","subject":"Bug: git log changes output depending on how the output is used","startedAt":"2018-10-25T15:26:48Z","lastAt":"2018-10-25T15:26:48Z","messageCount":1,"participants":["buckmartin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"361518","messageId":"CAJCHkCHPpZVPX2zeHQZWGKyCpHdFFHvNqn1Db0hsAPfTdjV-+A@mail.gmail.com","threadId":"49673","inReplyTo":null,"subject":"Bug: git log changes output depending on how the output is used","fromName":"buckmartin","fromEmail":"buckmartin@gmail.com","sentAt":"2018-10-25T15:26:35Z","receivedAt":"2018-10-25T15:26:48Z","isPatch":false,"sender":{"key":"buckmartin@gmail.com","avatar":null},"body":"I noticed that the piped output still prints the (HEAD -> ) :\n\n\n\ngit log --pretty=format:\"%d*%B\" --decorate-refs='refs/tags/*'\n\n*bar\n(tag: \"123\")*foo\n\n\n\n\n\ngit log --pretty=format:\"%d*%B\" --decorate-refs='refs/tags/*' > tmp.tmp\n\n(HEAD -> branch)*bar\n(tag: \"123\")*foo\n\n\n\nI would expect the output that is printed to console, not what's\npresent in tmp.tmp\n"}]}