On Fri, May 4, 2018 at 5:23 PM, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: >> > So that's what `info` does: it influences whether/where >> > the command is listed in `git help`'s output... Interesting. I thought the >> > lines here were trying to automate parts of the tab completion or >> > something. >> >> Oh it does many things. The completion part is coming (so yeah you >> don't need to update git-completion.bash at all, as long as you have a >> line here and use parse_options() ;-), but I think it's mainly for >> "git help" and command listing in "git help git" (this command for >> example should show up under the "Main porcelain commands" in that man >> page when you put a line here) > > I have a hard time believing that anything automated can infer from the > source code that branch-diff can accept the non-options in three different > formats, and what those formats look like... Yeah. For now it can only do options which is machine readable. But I have a big plan, so who knows :D -- Duy
