From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Cc: glep@gentoo.org, Sam James <sam@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH 0/1] Add 'notes' element to metadata.xml (GLEP 68)
Date: Tue, 5 Oct 2021 13:29:43 -0700 [thread overview]
Message-ID: <CAAr7Pr80ZoUEcO9ZwNXM_Kmmk2np2Qy9CBqF45SKAwetf66DfA@mail.gmail.com> (raw)
In-Reply-To: <20211005182739.2902646-1-sam@gentoo.org>
I thought we were going to go with the github-pages type route
(markdown, rendered online or locally.)
-A
On Tue, Oct 5, 2021 at 11:28 AM Sam James <sam@gentoo.org> wrote:
>
> This is a preliminary version/draft of a proposed change to
> GLEP 68.
>
> I'd like to introduce a method for developers to signal anything
> special about a package and how to correctly maintain it.
>
> Sam James (1):
> glep-0068: Add notes element for package maintenance instructions
>
> glep-0068.rst | 26 +++++++++++++++++++++++---
> 1 file changed, 23 insertions(+), 3 deletions(-)
>
> --
> 2.33.0
>
>
next prev parent reply other threads:[~2021-10-05 20:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 18:27 [gentoo-dev] [PATCH 0/1] Add 'notes' element to metadata.xml (GLEP 68) Sam James
2021-10-05 18:27 ` [gentoo-dev] [PATCH 1/1] glep-0068: Add notes element for package maintenance instructions Sam James
2021-10-05 19:09 ` Mike Gilbert
2021-10-05 19:42 ` Wolfgang E. Sanyer
2021-10-05 22:17 ` Andreas K. Huettel
2021-10-06 5:35 ` Ulrich Mueller
2021-10-05 19:09 ` [gentoo-dev] [PATCH 0/1] Add 'notes' element to metadata.xml (GLEP 68) Michał Górny
2021-10-05 20:13 ` Alessandro Barbieri
2021-10-06 5:28 ` Ulrich Mueller
2021-10-07 7:00 ` Matthew Marchese
2021-10-07 7:27 ` Ulrich Mueller
2021-10-05 20:29 ` Alec Warner [this message]
2021-10-05 20:36 ` Sam James
2021-10-05 21:21 ` Alec Warner
2021-10-06 5:37 ` Ulrich Mueller
2021-10-06 6:25 ` Alec Warner
2021-10-06 9:33 ` Ulrich Mueller
2022-03-04 0:35 ` Ionen Wolkens
2022-03-04 8:02 ` Joonas Niilola
2021-10-05 23:54 ` Joshua Kinard
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=CAAr7Pr80ZoUEcO9ZwNXM_Kmmk2np2Qy9CBqF45SKAwetf66DfA@mail.gmail.com \
--to=antarus@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=glep@gentoo.org \
--cc=sam@gentoo.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