16:25 <conchuod> mmind00: do you use b4's thank feature?

16:26 <mmind00> conchuod: yep ... though, now you make me worries that I accidentially sent a thanks message for a wrong patch :-)

16:27 <mmind00> conchuod: i.e. there shouldn't be one for riscv stuff ;-)

16:27 <mmind00> conchuod: i.e. b4 has "boundary issues" and seemingly tracks accross trees, so even when I fetch a riscv patch I need to kick it from the thanks list

16:35 <conchuod> No, I saw it on rockchip stuff

16:39 <mmind00> conchuod: then phew :-) ... but yeah b4 is just a great tool

16:39 <conchuod> I was just curious, that's all. Need to start automating some stuff

16:43 <conchuod> I've always wondered, do people generally type out review/ack tags? Or have some sort of macro for it

18:42 <mmind00> conchuod: as for Review/Tested tags I do tend to just write them out in a normal mail client ... there is that school of thought that one should at least add a bit of additional info in such a mail, so that a Reviewed-by is not simply an empty boilerplate statement ... so when going that route writing the tag itself also isn't that much more work ;-)

18:44 <mmind00> conchuod: no worries about the curious :-) ... I just started doubting myself then, because as I said b4 does not seem to track per git tree

19:08 <conchuod> mmind00: ik this is me being "lazy" but does it just spit out files that you can git send-email?

21:10 <mmind00> conchuod: not sure if I "get" your question, but b4 is handling the other way ... retrieving patch-series (adding all the Tested/Review tags that got sent as answers) and creating an mbox that you can "git am"

21:38 <conchuod> mmind00: no no, I meant for "b4 ty"

21:39 <conchuod> I use b4 am/b4 shazam all the time ;)

21:39 <mmind00> conchuod: ah ... yes, b4 creates the messages which then can be fed to git send-email ... which is the workflow I use

21:40 <conchuod> Cool, I wanted to know before I used it and accidentally sent a mail haha

21:40 <conchuod> thanks