From: Albert Cui <albertqcui@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Albert Cui via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org,
"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH v2] hooks: propose project configured hooks
Date: Mon, 5 Apr 2021 16:42:14 -0700 [thread overview]
Message-ID: <CAMbkP-TL3f9V4bGp3bDq_7=E47JKdh5ua2giRZKaUrvODOPWew@mail.gmail.com> (raw)
In-Reply-To: <8735w9knx4.fsf@evledraar.gmail.com>
On Fri, Apr 2, 2021 at 2:59 AM Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
>
>
> On Fri, Mar 26 2021, Albert Cui via GitGitGadget wrote:
>
> > From: Albert Cui <albertqcui@gmail.com>
>
> Formatting nit:
>
> > +Git has https://git-scm.com/docs/githooks[hooks] functionality to allow users to
> > [...]
> > +local checks of code e.g. linting. As documented in
> > +https://git-scm.com/docs/gitfaq#_hooks[gitfaq], in some cases, server-side
> > +checks may be more appropriate, especially since developers can always skip
>
> This should be a linkgit:* even in the technical/ directory, should it
> not? We build docs on git-scm.com (among others), but in our source tree
> we should be using linking syntax, not linking to our own already-built
> docs on some website.
Yes, thanks. Good catch.
next prev parent reply other threads:[~2021-04-05 23:42 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 22:03 [PATCH] hooks: propose repository owner configured hooks Albert Cui via GitGitGadget
2021-03-18 22:29 ` Junio C Hamano
2021-03-18 23:45 ` Albert Cui
2021-03-19 1:28 ` brian m. carlson
2021-03-19 10:27 ` Ævar Arnfjörð Bjarmason
2021-04-06 0:35 ` Albert Cui
2021-04-07 22:47 ` Ævar Arnfjörð Bjarmason
2021-06-21 19:36 ` Jonathan Tan
2021-06-21 20:35 ` Ævar Arnfjörð Bjarmason
2021-03-26 1:43 ` [PATCH v2] hooks: propose project " Albert Cui via GitGitGadget
2021-03-29 23:20 ` Emily Shaffer
2021-04-01 20:02 ` Albert Cui
2021-03-30 15:24 ` Derrick Stolee
2021-04-05 22:45 ` Albert Cui
2021-04-05 23:09 ` Junio C Hamano
2021-04-05 23:40 ` Albert Cui
2021-04-06 0:13 ` Junio C Hamano
2021-04-06 0:27 ` Albert Cui
2021-04-06 23:15 ` brian m. carlson
2021-04-07 7:53 ` Ævar Arnfjörð Bjarmason
2021-04-07 13:09 ` Derrick Stolee
2021-04-07 18:40 ` Albert Cui
2021-04-07 20:02 ` Junio C Hamano
2021-04-07 22:23 ` Ævar Arnfjörð Bjarmason
2021-04-15 16:52 ` Ed Maste
2021-04-15 19:41 ` Junio C Hamano
2021-04-15 20:37 ` Ed Maste
2021-04-15 20:50 ` Junio C Hamano
2021-04-15 22:28 ` brian m. carlson
2021-04-02 9:59 ` Ævar Arnfjörð Bjarmason
2021-04-05 23:42 ` Albert Cui [this message]
2021-04-02 10:30 ` Ævar Arnfjörð Bjarmason
2021-04-03 0:58 ` Albert Cui
2021-04-24 1:38 ` [PATCH v3] " Albert Cui via GitGitGadget
2021-04-28 2:48 ` Junio C Hamano
2021-05-05 19:11 ` [PATCH v4] " Albert Cui via GitGitGadget
2021-06-03 3:31 ` Jonathan Tan
2021-06-03 20:16 ` Albert Cui
2021-06-03 22:10 ` Jonathan Tan
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='CAMbkP-TL3f9V4bGp3bDq_7=E47JKdh5ua2giRZKaUrvODOPWew@mail.gmail.com' \
--to=albertqcui@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=sandals@crustytoothpaste.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).