From: Sam James <sam@gentoo.org>
To: c-std-porting@lists.linux.dev
Subject: Re: Best method to share that something is broken + patches?
Date: Tue, 22 Nov 2022 07:55:27 +0000 [thread overview]
Message-ID: <87sfibfmn8.fsf@gentoo.org> (raw)
In-Reply-To: <87zgcjfmyi.fsf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
Sam James <sam@gentoo.org> writes:
> [[PGP Signed Part:Undecided]]
>
> We didn't really have a proper chance to discuss how the list mechanics
> should work yet,
> as we got caught a bit off guard by the LWN (and then Phoronix)
> articles.
>
> [...]
>
> I'm thinking maybe a shared git repository for the patches (and/or just
> links to bug
> reports), while we keep the list for discussion of non-trivial issues,
> or significant
> PSAs (including a major package being broken, especially if it doesn't
> get frequent
> releases) rather than polluting the ML with some random package which
> only a single
> distro happens to maintain.
We may also need some weak guidelines on package name normalisation
and suggestions welcome for the structure of any repo if we pursue
that option.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next prev parent reply other threads:[~2022-11-22 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 7:48 Best method to share that something is broken + patches? Sam James
2022-11-22 7:55 ` Sam James [this message]
2022-11-22 12:08 ` Florian Weimer
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=87sfibfmn8.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=c-std-porting@lists.linux.dev \
/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.