Re: [PATCH 02/18] Add a new builtin: branch-diff
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- May 4, 2018, 15:23 UTC
- Message-ID
- <nycvar.QRO.7.76.6.1805041723050.77@tvgsbejvaqbjf.bet>
- In-Reply-To
- <CACsJy8AnWC8bLfhj25quzHokber-wrWdSsJiCDra=Ymr++0-nQ@mail.gmail.com>
Hi Duy,
On Fri, 4 May 2018, Duy Nguyen wrote:
Show 7 quoted lines
> On Fri, May 4, 2018 at 9:23 AM, Johannes Schindelin > <Johannes.Schindelin@gmx.de> wrote: > > Oh, okay. It was not at all clear to me what the exact format and role of > > these lines are... > > Noted. I'm making more updates in this file in another topic and will > add some explanation so the next guy will be less confused.
Thank you!
Show 11 quoted lines
> > 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...
Ciao, Dscho