From: Jonathan Corbet <corbet@lwn.net>
To: Kees Cook <keescook@chromium.org>
Cc: Linus Walleij <linus.walleij@linaro.org>, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: Document how to get links with git am
Date: Mon, 18 Nov 2019 11:46:07 -0700 [thread overview]
Message-ID: <20191118114607.14158343@lwn.net> (raw)
In-Reply-To: <201911151516.94D79DFB70@keescook>
On Fri, 15 Nov 2019 15:18:22 -0800
Kees Cook <keescook@chromium.org> wrote:
> > - I wonder if the hook script should just go under tools/ somewhere for
> > people to grab.
>
> Do we have anywhere to put these kinds of things, or do we need create
> something new?
I don't think there's a place now; I bet, though, if we were to create a
tools/git it would get other useful stuff before too long.
jon
next prev parent reply other threads:[~2019-11-18 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 13:30 [PATCH] Documentation: Document how to get links with git am Linus Walleij
2019-11-15 20:00 ` Jonathan Corbet
2019-11-15 23:18 ` Kees Cook
2019-11-18 18:46 ` Jonathan Corbet [this message]
2019-11-15 23:32 ` Linus Walleij
2019-11-18 18:52 ` Jonathan Corbet
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=20191118114607.14158343@lwn.net \
--to=corbet@lwn.net \
--cc=keescook@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
/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).