| Message ID | 1499371624-9639-1-git-send-email-rodrigo.vivi@intel.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
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>`_.
On Mon, 2017-07-10 at 13:29 +0300, Jani Nikula wrote: > 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> could I just squash, keep the ack and merge? > > > > > --- > > 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>`_. >
merged, thanks On Mon, Jul 10, 2017 at 12:25 PM, Vivi, Rodrigo <rodrigo.vivi@intel.com> wrote: > On Mon, 2017-07-10 at 13:29 +0300, Jani Nikula wrote: >> 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> > > could I just squash, keep the ack and merge? > >> >> >> >> > --- >> > 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>`_. >> > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
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>`_.
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> --- drm-intel.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)