| 00:41.05 | *** join/#brlcad LordOfBikes (~armin@dslb-092-074-236-015.092.074.pools.vodafone-ip.de) |
| 09:55.05 | *** join/#brlcad yorik (~yorik@203.185-200-80.adsl-dyn.isp.belgacom.be) |
| 10:28.12 | *** join/#brlcad Caterpillar (~caterpill@unaffiliated/caterpillar) |
| 18:00.40 | *** join/#brlcad yukonbob (~bch@S01069050ca2cbf63.ok.shawcable.net) |
| 18:00.44 | yukonbob | hello #brlcad |
| 19:01.24 | Sean[m] | kanzure: they're preserved in git notes. |
| 19:02.13 | Sean[m] | if you run git fetch origin refs/notes/commits:refs/notes/commits, you'll see them on git log |
| 23:16.16 | kanzure | Sean[m]: thank you |
| 23:18.06 | Sean[m] | kanzure: that's not to say we'll keep in that way. notes are somewhat cumbersome to maintain as they can get disassociated if a commit is edited. we may end up simply appending the notes to the commit log. thoughts? ] |
| 23:19.26 | kanzure | depends on how it is appended to the commit log i suppose |
| 23:19.41 | kanzure | most convenient place is in hte commit message, but actually, there is room for extra data in the signature field of git commits |
| 23:19.48 | kanzure | this is where opentimestamps stuffs timestamps |
| 23:21.43 | kanzure | https://github.com/opentimestamps/opentimestamps-client/blob/master/otsclient/git_gpg_wrapper.py#L137..L138 |