All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [maintainer-tools RFC PATCH] drm-intel: Link to .html	instead of .rst
Date: Mon, 10 Jul 2017 13:29:08 +0300	[thread overview]
Message-ID: <87shi4pouj.fsf@nikula.org> (raw)
In-Reply-To: <1499371624-9639-1-git-send-email-rodrigo.vivi@intel.com>

On Thu, 06 Jul 2017, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> Ideally .rst would referrence .rst with :ref:`` but since
> these documentation are different repository we cannot link
> like this. However I believe the main usage is through the
> compiled html pages and since we already reference another
> .html here I believe we should use our daily compiled doc.
>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

As I wrote in my other mail, I think this is better.

Acked-by: Jani Nikula <jani.nikula@intel.com>



> ---
>  drm-intel.rst | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drm-intel.rst b/drm-intel.rst
> index 5dcb7d8..fa1e9bc 100644
> --- a/drm-intel.rst
> +++ b/drm-intel.rst
> @@ -189,7 +189,7 @@ the appropriate branches.
>  
>  If possible, the commit message should also contain a Fixes: tag as described in
>  `Documentation/process/submitting-patches
> -<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst>`_
> +  <https://01.org/linuxgraphics/gfx-docs/drm/process/submitting-patches.html>`_
>  to aid the maintainers in identifying the right branch.
>  
>  Requesting Fixes Cherry-Pick Afterwards
> @@ -199,7 +199,7 @@ It's not uncommon for a patch to have been committed before it's identified as a
>  fix needing to be backported.
>  
>  If the patch is already in Linus' tree, please follow `stable kernel rules
> -<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/stable-kernel-rules.rst>`_.
> +<https://01.org/linuxgraphics/gfx-docs/drm/process/stable-kernel-rules.html>`_.
>  
>  Otherwise, send an email to intel-gfx@lists.freedesktop.org and
>  drm-intel-fixes@lists.freedesktop.org containing the subject of the patch, the
> @@ -361,7 +361,7 @@ An inexhaustive list of details to check:
>  
>  * The patch conforms to `Documentation/process/submitting-patches
>  
> -  <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst>`_
> +  <https://01.org/linuxgraphics/gfx-docs/drm/process/submitting-patches.html>`_
>  
>  * The commit message is sensible, and includes adequate details and references.
>  
> @@ -411,7 +411,7 @@ On Confidence, Complexity, and Transparency
>  
>  * Reviewed-by. All patches must be reviewed, no exceptions. Please see
>    "Reviewer's statement of oversight" in `Documentation/process/submitting-patches
> -  <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst>`_
> +  <https://01.org/linuxgraphics/gfx-docs/drm/process/submitting-patches.html>`_
>    and `review training
>    <http://blog.ffwll.ch/2014/08/review-training-slides.html>`_.

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-07-10 10:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 20:07 [maintainer-tools RFC PATCH] drm-intel: Link to .html instead of .rst Rodrigo Vivi
2017-07-10 10:29 ` Jani Nikula [this message]
2017-07-10 19:25   ` Vivi, Rodrigo
2017-07-10 22:00     ` Rodrigo Vivi

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=87shi4pouj.fsf@nikula.org \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.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 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.