|author||Eric Wong <email@example.com>||2018-12-12 23:57:02 +0000|
|committer||Eric Wong <firstname.lastname@example.org>||2018-12-13 00:00:42 +0000|
Archives are crucial to preserving history and knowledge in Free Software projects, so promote them for projects we depend on. Naq lrf, gur nepuviny fbsgjner qrirybcrq sbe nepuvivat gur havpbea znvyvat yvfg unf ybat fhecnffrq gur hfrshyarff bs havpbea vgfrys :C
1 files changed, 5 insertions, 2 deletions
@@ -39,6 +39,7 @@ https://bugs.ruby-lang.org/ and discuss+fix them on the ruby-core
list at mailto:email@example.com
Subscription to post is required to ruby-core, unfortunately:
+Unofficial archives are available at: https://public-inbox.org/ruby-core/
For uncommon bugs in Rack, we may forward bugs to
mailto:firstname.lastname@example.org and discuss there.
@@ -46,6 +47,7 @@ Subscription (without any web UI or Google account) is possible via:
Note: not everyone can use the proprietary bug tracker used by Rack,
but their mailing list remains operational.
+Unofficial archives are available at: https://public-inbox.org/rack-devel/
Uncommon bugs we encounter in the Linux kernel should be Cc:-ed to the
Linux kernel mailing list (LKML) at mailto:email@example.com
@@ -54,11 +56,12 @@ and subsystem maintainers such as mailto:firstname.lastname@example.org
involved with any problematic commits (including those in the
Signed-off-by: and other trailer lines). No subscription is necessary,
and the our mailing list follows the same conventions as LKML for
-interopability. There is a kernel.org Bugzilla instance, but it is
-ignored by most developers.
+interopability. Archives are available at https://lore.kernel.org/lkml/
+There is a kernel.org Bugzilla instance, but it is ignored by most.
Likewise for any rare glibc bugs we might encounter, we should Cc:
+Unofficial archives are available at: https://public-inbox.org/libc-alpha/
Keep in mind glibc upstream does use Bugzilla for tracking bugs: