Sverre Rabbelier [off-list ref] writes:
... Should we have some way to queue patches like
this, or would someone have to resend after the appropriate release?
For this particular case, I do not think it is worth _my_ time to keep
maintaining that patch.
It is understandable that a new person will be hurt if
$ git ls-remote -h
does not give a short-help message and instead try to contact and show the
origin repository which may not even exist, and that is why I sent a fix.
But would anybody gets hurt if
$ git ls-remote -h origin
$ git ls-remote -h git://git.kernel.org/pub/git/git.git
kept working as they do today, given that we do not advertise -h as
a synonym in "git ls-remote -h" output?
That is why I said "I am not opposed to", and not "I'd volunteer to do
that". It's not worth my time, but since you brought it up, you may care
more about it.