Re: Best method to share that something is broken + patches?

--=-=-=
Content-Type: text/plain


Sam James <[email protected]> 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.

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iOUEARYKAI0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCY3yAm18UgAAAAAAuAChp
c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB
NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MA8cc2FtQGdlbnRv
by5vcmcACgkQc4QJ9SDfkZD8fgEAwjspG59pnJe7ByBiQySiHhqJR2gGtJ9vtkZC
fY/f2+4A/RTjCHyKohG/QAQjYHUT8MlBx4hJf/Pcuy3sSs2kZVEN
=HOLK
-----END PGP SIGNATURE-----
--=-=-=--