git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH] doc: simplify man version
Date: Tue, 11 Apr 2023 09:30:00 -0700	[thread overview]
Message-ID: <xmqqwn2i9ybb.fsf@gitster.g> (raw)
In-Reply-To: 64349c7dc4f49_7452943c@chronos.notmuch

Felipe Contreras <felipe.contreras@gmail.com> writes:

> Junio C Hamano wrote:
>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>> 
>> > diff --git a/Documentation/Makefile b/Documentation/Makefile
>> > index a6ba5bd460..4721b000c1 100644
>> > --- a/Documentation/Makefile
>> > +++ b/Documentation/Makefile
>> > @@ -150,8 +150,7 @@ ASCIIDOC_HTML = xhtml11
>> >  ASCIIDOC_DOCBOOK = docbook
>> >  ASCIIDOC_CONF = -f asciidoc.conf
>> >  ASCIIDOC_COMMON = $(ASCIIDOC) $(ASCIIDOC_EXTRA) $(ASCIIDOC_CONF) \
>> > -		-amanversion=$(GIT_VERSION) \
>> > -		-amanmanual='Git Manual' -amansource='Git'
>> > +		-amanmanual='Git Manual' -amansource='Git $(GIT_VERSION)'
>> >  ASCIIDOC_DEPS = asciidoc.conf GIT-ASCIIDOCFLAGS
>> >  TXT_TO_HTML = $(ASCIIDOC_COMMON) -b $(ASCIIDOC_HTML)
>> >  TXT_TO_XML = $(ASCIIDOC_COMMON) -b $(ASCIIDOC_DOCBOOK)
>> 
>> Is this a complete patch,
>
> Yes it is complete.

Good.

> I don't know know what could give this impression, given that a link to
> the documentation and the link to the source code was given:
> ...
> The code clearly tests for empty strings:
>
>   test="not($Name = '') and not($Version = '')

This part is exactly what I meant.  The readers of "git log"
shouldn't have to dig to external source material and find that
line to convince themselves why this is safe thing to do.

> And it's not clear to me what else it would be checking for.

Good.  The job of reviewers is not about nitpicking, but work with
and help a patch author to polish the patch text (both proposed log
message or diff) by pointing out what the author may have thought
obvious to everybody, because it was obvious to the author, but may
not be so obvious.  The goal is not to convince reviewers how the
patch text is correct in review discussion thread.  The goal is to
use reviewers' input to identify such parts of the patch text that
needs clarifying and update the patch text.  It is to avoid future
readers of "git log -p" to ask the same question, because unlike
reviewers, they will not have the original author readily available
to answer their questions.

Thanks.

  reply	other threads:[~2023-04-11 16:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-08  0:18 [PATCH] doc: simplify man version Felipe Contreras
2023-04-08 22:45 ` Junio C Hamano
2023-04-09 19:08   ` Jeff King
2023-04-10 23:41     ` Felipe Contreras
2023-04-10 23:43     ` Junio C Hamano
2023-04-10 23:32   ` Felipe Contreras
2023-04-11 16:30     ` Junio C Hamano [this message]
2023-04-16  3:45 ` Felipe Contreras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqwn2i9ybb.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).