[Intel-gfx] [maintainer-tools PATCH] drm-intel: Fix links to torvalds documentation.

[Jani Nikula]

On Thu, 06 Jul 2017, Rodrigo Vivi <rodrigo.vivi at intel.com> wrote:
> All process related docs has moved to the new "process" folder,
> but also all .txt migrated to .rst as well.

We could point at the generated documentation at [1] or [2] instead of
git trees now.

BR,
Jani.

[1] https://www.kernel.org/doc/html/latest/
[2] https://01.org/linuxgraphics/gfx-docs/drm/

>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi at intel.com>
> ---
>  drm-intel.rst | 15 ++++++++-------
>  1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/drm-intel.rst b/drm-intel.rst
> index 4699171..5dcb7d8 100644
> --- a/drm-intel.rst
> +++ b/drm-intel.rst
> @@ -188,8 +188,8 @@ The maintainers will cherry-pick labeled patches from drm-intel-next-queued to
>  the appropriate branches.
>  
>  If possible, the commit message should also contain a Fixes: tag as described in
> -`Documentation/SubmittingPatches
> -<https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches>`_
> +`Documentation/process/submitting-patches
> +<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst>`_
>  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/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/stable_kernel_rules.txt>`_.
> +<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/stable-kernel-rules.rst>`_.
>  
>  Otherwise, send an email to intel-gfx at lists.freedesktop.org and
>  drm-intel-fixes at lists.freedesktop.org containing the subject of the patch, the
> @@ -359,8 +359,9 @@ Detail Check List
>  
>  An inexhaustive list of details to check:
>  
> -* The patch conforms to `Documentation/SubmittingPatches
> -  <https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches>`_.
> +* 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>`_
>  
>  * The commit message is sensible, and includes adequate details and references.
>  
> @@ -409,8 +410,8 @@ On Confidence, Complexity, and Transparency
>    list, IRC, in person, in a meeting) but must be added to the commit.
>  
>  * Reviewed-by. All patches must be reviewed, no exceptions. Please see
> -  "Reviewer's statement of oversight" in `Documentation/SubmittingPatches
> -  <https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches>`_
> +  "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>`_
>    and `review training
>    <http://blog.ffwll.ch/2014/08/review-training-slides.html>`_.

-- 
Jani Nikula, Intel Open Source Technology Center