Lucas Seiki Oshiro <lucasseikioshiro@xxxxxxxxx> writes: >> Besides, wouldn't it possible that field may have to contain any >> end-user specified key, including <LF>? > > In `repo info`, no. This way, it's safe to parse everything before > the first <LF> as the key and everything between <LF> and <NUL> as > the value. OK. Even "git config" punts there by restricting the subsection part of the configuration variable name by forbidding LF and NUL in it ;-) So, I guess we are OK here. Thanks for thinking it through.
