From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Trupti <trupti@linux.ibm.com>
Cc: debian-powerpc <debian-powerpc@lists.debian.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
gentoo-powerpc@lists.gentoo.org
Subject: Re: Github tracker for PowerPC issues
Date: Thu, 22 Jan 2026 07:55:56 +0100 [thread overview]
Message-ID: <1534D914-DAFF-4008-87ED-E887BA0DC070@physik.fu-berlin.de> (raw)
In-Reply-To: <f80cd9f9b91966862ece4bb270460198@linux.ibm.com>
> On Jan 22, 2026, at 7:47 AM, Trupti <trupti@linux.ibm.com> wrote:
>
> Thanks for sharing this information. However, the issues at https://github.com/linuxppc/issues/issues are mostly related to the core Linux kernel and toolchain.
>
> For Debian-specific work, we need a separate issue tracker: https://github.com/linuxppc/Debian/issues, where Debian-related issues can be reported.
But I’m not talking about Debian-specific issues. Tracking Debian-specific issues happens in Debian.
When I report an issue in the GHC Haskell compiler on PowerPC, it belongs in the existing tracker. Doesn’t it?
Adrian
next prev parent reply other threads:[~2026-01-22 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 20:43 Github tracker for PowerPC issues John Paul Adrian Glaubitz
2026-01-22 6:46 ` Trupti
2026-01-22 6:55 ` John Paul Adrian Glaubitz [this message]
2026-01-22 7:14 ` Trupti
2026-01-22 7:41 ` John Paul Adrian Glaubitz
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=1534D914-DAFF-4008-87ED-E887BA0DC070@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-powerpc@lists.debian.org \
--cc=gentoo-powerpc@lists.gentoo.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=trupti@linux.ibm.com \
/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