# 'git --grep' doesn't grep notes? 2 messages from 2012-08-27 to 2012-08-27. Participants: Todd A. Jacobs, Andreas Schwab. Thread: https://gitlist.dev/t/31365 ## Todd A. Jacobs, 2012-08-27 18:18 Subject: 'git --grep' doesn't grep notes? Message-ID: URL: https://gitlist.dev/e/CAPRhCbvnRqUpKcw_E383ekG_M0O2a%2BcTTixUQtU-0mtj3V%3D7uw%40mail.gmail.com ``` I have a note attached to a commit, but the text of the note isn't treated as part of the commit for the purposes of grep. For example: mkdir /tmp/foo cd /tmp/foo git init git commit --allow-empty -m 'Blank commit.' git notes add -m 'Find me!' git log --show-notes --regexp-ignore-case --grep=find This doesn't match anything. Expected behavior is that this will match the commit that contains "Find me!" in the notes. As an example use case, consider ticket integration, where you may want to add a ticket ID to a commit long after it's been pushed. You don't want to rewind the branch, or push a rebase, so a note seems like a sensible place to store a ticket ID. However, if the notes aren't part of the commit, this will break integration with tools like Pivotal Tracker that search the commits, and it will also require you to use an external grep and some custom parsing to find related commit IDs. I'm sure there are other use cases. This just happens to be mine right now. What is the right way to include notes in log searches, especially if the end goal is to find the related commit ID? ``` ## Andreas Schwab, 2012-08-27 19:09 Subject: Re: 'git --grep' doesn't grep notes? Message-ID: URL: https://gitlist.dev/e/m2harob19o.fsf%40igel.home In-Reply-To: ``` "Todd A. Jacobs" writes: > What is the right way to include notes in log searches, especially if > the end goal is to find the related commit ID? You can git grep on refs/notes/commits and s,/,,g on the file name found. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." ```