Change Details

When @multichill and I were investigating T90156 at Lyon , git was showing one file as modified after a fresh clone of master. This was caused by git ident replacing $Id in bot.handle_args . As a result, it is quite hard to develop on the Redhat system, as this additional change keeps being included. IIRC, the git version was greater than 1.7.0.4 which is mentioned in bot.py . One solution is to remove these idents from all files and the chunk of code supporting them in bot.handle_args. Another is to obfuscate the $Id in bot.handle_args even more so old versions of git cant recognise it.

When @multichill and I were investigating T90156 at Lyon , git was showing one file as modified after a fresh clone of master. This was caused by git ident replacing $Id in bot.handle_args . As a result, it is quite hard to develop on the Redhat system, as this additional change keeps being included. IIRC, the git version was greater than 1.7.0.4 which is mentioned in bot.py . One solution is to remove these idents from all files and the chunk of code supporting them in bot.handle_args. (T87409) Another is to obfuscate the $Id in bot.handle_args even more so old versions of git cant recognise it.

When @multichill and I were investigating T90156 at Lyon , git was showing one file as modified after a fresh clone of master. This was caused by git ident replacing $Id in bot.handle_args . As a result, it is quite hard to develop on the Redhat system, as this additional change keeps being included. IIRC, the git version was greater than 1.7.0.4 which is mentioned in bot.py . One solution is to remove these idents from all files and the chunk of code supporting them in bot.handle_args. (T87409) Another is to obfuscate the $Id in bot.handle_args even more so old versions of git cant recognise it.