From: Junio C Hamano <gitster@pobox.com>
To: Justin Tobler <jltobler@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] doc: clarify post-receive hook behavior
Date: Mon, 15 Jul 2024 11:44:29 -0700 [thread overview]
Message-ID: <xmqqjzhm3376.fsf@gitster.g> (raw)
In-Reply-To: <dzdoaldgm5sk25ll57okroqcnhqurtoqmo7d5xsjnrjpgveqzx@63w4uav6jtd6> (Justin Tobler's message of "Mon, 15 Jul 2024 13:22:36 -0500")
Justin Tobler <jltobler@gmail.com> writes:
> I think it makes the most sense to drop the link:*html used here and
> just rely on the linkgit: reference. I'll adjust this in v3. Thanks for
> the feedback.
That sounds like a sensible and conservative approach.
Thanks.
next prev parent reply other threads:[~2024-07-15 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 22:47 [PATCH] doc: clarify post-receive hook behavior Justin Tobler
2024-07-12 23:11 ` Junio C Hamano
2024-07-14 18:54 ` Justin Tobler
2024-07-14 19:46 ` [PATCH v2] " Justin Tobler
2024-07-15 15:46 ` Junio C Hamano
2024-07-15 18:22 ` Justin Tobler
2024-07-15 18:44 ` Junio C Hamano [this message]
2024-07-15 18:37 ` [PATCH v3] " Justin Tobler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqjzhm3376.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jltobler@gmail.com \
/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.
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 NNTP newsgroup(s).