All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] Documentation: Document how to get links with git am
Date: Mon, 18 Nov 2019 11:52:22 -0700	[thread overview]
Message-ID: <20191118115222.77fa9930@lwn.net> (raw)
In-Reply-To: <CACRpkdbr=y6eApvZcqnaU0He+B5QBE9JCezuQhEjEjpU5ZHW1A@mail.gmail.com>

On Sat, 16 Nov 2019 00:32:35 +0100
Linus Walleij <linus.walleij@linaro.org> wrote:

> > Seems generally useful.  I have a couple of overall questions...
> >
> >  - Might this be better placed in the maintainer manual?  It is more
> >    likely to be relevant to that audience, methinks.  
> 
> Oh that exists now, Documentation/maintainer? Sure I fix.

Indeed it exists...it's a little sparse at the moment, but that's what
I'm trying to improve...:)

> >  - I wonder if the hook script should just go under tools/ somewhere for
> >    people to grab.  
> 
> Does one exclude the other?
> 
> Can we place it under tools/scripts/git and somehow source the contents into
> this file so you can also see it?

That could be done...something like:

	.. include:: ../../scripts/git/add-link
		:literal:

should do it...obviously adjusted for the actual name and location of the
script.

Of course, cutting the script from the document isn't all that big a deal
either; that was mostly just me wondering.

Thanks,

jon

      reply	other threads:[~2019-11-18 18:52 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
2019-11-15 23:32   ` Linus Walleij
2019-11-18 18:52     ` Jonathan Corbet [this message]

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=20191118115222.77fa9930@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.