Recently, I followed the discussion [1] and I thought: let's look at the
manual pages to see what options Git currently uses -- just out of
curiosity and for learning about Git.

That were 160 manual pages to visit and if I counted correctly, there
are 1160 different option strings -- some of them related and only
differing in details.

The attached file doesn't always say anything about semantics that
sometimes is totally different (for -h, for example).

I thought that could be interesting to some of you, as well, so I send
it to the list.

Some points I noticed:

- SYNOPSIS not always matches OPTIONS (e.g. git(1)) and in those cases
  [<options>] would probably a better solution.

- Options that require arguments are often listed without those
  arguments in OPTIONS but those arguments are talked about and one has
  to go to SYNOPSIS to come to know the order of those arguments
  (e.g. git branch -m)

Should you wonder about the sorting, I tried to stick to the following
rules:

- Take the strings as they appear in the OPTIONS sections -- no splitting.
- Primarily sort by letters and numbers.
- Sort by the first option, then by the second.
  Arguments are only used within those groups.
- I changed the rules on the way, so there may be errors.

Disclaimer: because manually created this file isn't 100% correct but I
            gave my best.  On the way I noticed that sometimes options
            appear at unexpected places, so I for sure missed some.



At least this perhaps serves amusing purposes ;-)

Who knows, perhaps you think git-options(7) would be a valuable
addition.  I think it can be automatically generated with a moderate
amount of work.

Or the attached file could be used for some SoC micro-procect or the
like...

Dirk

[1] https://lore.kernel.org/git/ef5958e1-af3f-4869-b0e3-ff1448c0d73c@gmail.com/T/#t