From: Carlos O'Donell <carlos@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
cti-tac@lists.linuxfoundation.org
Subject: Re: [PATCH 1/5] projects/glibc: slightly adjust the structure
Date: Thu, 7 Mar 2024 15:22:46 -0500 [thread overview]
Message-ID: <191eb22c-ec30-4f01-a7b9-b7b9fa5ae0fb@redhat.com> (raw)
In-Reply-To: <20240307193019.4028812-2-siddhesh@gotplt.org>
On 3/7/24 14:30, Siddhesh Poyarekar wrote:
> Add some subheadings and fix a broken link.
>
The HTML part is not OK. Please check format of cross doc ref.
> Signed-off-by: Siddhesh Poyarekar <siddhesh@gotplt.org>
> ---
> source/projects/glibc.rst | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/source/projects/glibc.rst b/source/projects/glibc.rst
> index 7e6604a..a400dab 100644
> --- a/source/projects/glibc.rst
> +++ b/source/projects/glibc.rst
> @@ -5,6 +5,9 @@ In 2024 the goal is to migrate the glibc project to use CTI services.
>
> The community feedback was collected from July to August 2023.
>
> +Current Status
> +--------------
OK.
> +
> The `GNU Maintainers for the glibc project
> <https://sourceware.org/glibc/wiki/MAINTAINERS#Project_stewards_.28GNU_package_maintainers.29>`_
> were asked to make a decision on switching to the services provided by
> @@ -24,13 +27,17 @@ this document to provide assurances that FOSS would be used to provide
> services and that there was a checking mechanism in place for services
> to remain FOSS.
>
> -Next steps:
> +Next steps
> +----------
OK.
>
> * Revisit discussion with Paul Eggert and attain resolution in March 2024
> to move forward.
>
> Posted originally here: https://inbox.sourceware.org/libc-alpha/45e98807-908f-0968-b6fe-5dbb0af265b1@redhat.com/
>
> +Service migration
> +-----------------
OK.
> +
> The following is the suggested list of services to be migrated (with notes):
>
> * Mailing lists
> @@ -81,7 +88,7 @@ The following is the suggested list of services to be migrated (with notes):
> * Isolate BBB from other services.
>
> The current list of glibc services were put together as part of the
> -CTI TAC `glibc service enumeration <./enum>`_.
> +CTI TAC `glibc service enumeration <./enum.html>`_.
I don't think this is correct.
I agree the website link is broken, but it has to be a cross-document reference
that works when generated as html (rather than assume html).
>
> -----------------
>
--
Cheers,
Carlos.
next prev parent reply other threads:[~2024-03-07 20:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 19:30 [PATCH 0/5] Multiple website cleanups Siddhesh Poyarekar
2024-03-07 19:30 ` [PATCH 1/5] projects/glibc: slightly adjust the structure Siddhesh Poyarekar
2024-03-07 20:22 ` Carlos O'Donell [this message]
2024-03-07 20:38 ` Siddhesh Poyarekar
2024-03-07 20:45 ` Carlos O'Donell
2024-03-07 19:30 ` [PATCH 2/5] Add a toplevel README Siddhesh Poyarekar
2024-03-07 20:24 ` Carlos O'Donell
2024-03-07 20:25 ` Carlos O'Donell
2024-03-07 21:00 ` Siddhesh Poyarekar
2024-03-07 21:06 ` Carlos O'Donell
2024-03-07 21:54 ` Siddhesh Poyarekar
2024-03-07 19:30 ` [PATCH 3/5] services: Clean up links to projects Siddhesh Poyarekar
2024-03-07 20:25 ` Carlos O'Donell
2024-03-07 19:30 ` [PATCH 4/5] tac/audit: Minor cleanups Siddhesh Poyarekar
2024-03-07 20:26 ` Carlos O'Donell
2024-03-07 19:30 ` [PATCH 5/5] faq: Reformat so that it's not a list Siddhesh Poyarekar
2024-03-07 20:27 ` Carlos O'Donell
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=191eb22c-ec30-4f01-a7b9-b7b9fa5ae0fb@redhat.com \
--to=carlos@redhat.com \
--cc=cti-tac@lists.linuxfoundation.org \
--cc=siddhesh@gotplt.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).