Re: [PATCH/RFC 5/5] add tests for checking the behaviour of "unset.variable"

Junio C Hamano [off-list ref] writes:

That is why I said "unset.variable" is unworkable with existing "git
config" command line.  Always appending at the end is usable for
ordinary variables, but for unset.variable, it is most likely the
least useful thing to do.  You can explain "among 47 different
things it could do, we chose to do the most useless thing, because
that is _consistent_ with how the ordinary variables are placed in
the cofiguration file" in the documentation but it forgets to
question if unset.variable should be treated the same way as
ordinary variables in the first place.

This is a tangent, but the above also applies to the "include.path".