On Fri, Mar 15, 2024 at 6:19 PM Junio C Hamano <gitster@xxxxxxxxx> wrote: > ---comment <value>:: > - Append a comment to new or modified lines. A '#' character will be > - unconditionally prepended to the value. The value must not contain > - linefeed characters (no multi-line comments are permitted). > +--comment <message>:: > + Append a comment at the end of new or modified lines. > + Unless _<message>_ begins with "#", a string "# " (hash > + followed by a space) is prepended to it. The _<message>_ must not > + contain linefeed characters (no multi-line comments are permitted). In an earlier review, you wrote about the potential difficulties and issues surrounding comments other than the simple "inline" comments tackled by this patch. Do we foresee a future in which git-config may be extended to handle automation of comments other than inline? If so, do we really want to lock ourselves into having the generic option `--comment=<message>` be restricted to only inline comments? Or would it be better to plan for the future by instead having some sort of annotation which indicates that we are requesting (or dealing with) only inline comments, such as `--inline-comment=<message>` or `--comment=inline:<message>`?
