public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Trupti <trupti@linux.ibm.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
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 12:16:33 +0530	[thread overview]
Message-ID: <f80cd9f9b91966862ece4bb270460198@linux.ibm.com> (raw)
In-Reply-To: <a8c239b497a3986fa20556b5aa54b8e2c8d56b17.camel@physik.fu-berlin.de>


Hello Adrian,


On 2026-01-22 02:13, John Paul Adrian Glaubitz wrote:
> Hi,
> 
> I just noticed that similar to the issue tracker I created for SPARC
> [1], there is an
> issue tracker for PowerPC [2].
> 
> The idea is to track any issues specific to a certain architecture in
> a central, prominent
> location so these become visible to any distribution maintainer and
> PowerPC upstream developer.
> 
> Thus, if you spot a bug affecting PowerPC, please report it in [2].
> 
> Thanks,
> Adrian
> 
>> [1] https://github.com/sparclinux/issues/issues
>> [2] https://github.com/linuxppc/issues/issues

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.

I will share the link to this issue tracker shortly.


Thanks,
Trupti


  reply	other threads:[~2026-01-22  7:10 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 [this message]
2026-01-22  6:55   ` John Paul Adrian Glaubitz
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=f80cd9f9b91966862ece4bb270460198@linux.ibm.com \
    --to=trupti@linux.ibm.com \
    --cc=debian-powerpc@lists.debian.org \
    --cc=gentoo-powerpc@lists.gentoo.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linuxppc-dev@lists.ozlabs.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