From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Romain Naour <romain.naour@gmail.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH] docs, package/gcc: switch to Gitlab issue tracker
Date: Thu, 13 Jun 2024 23:41:19 +0200 [thread overview]
Message-ID: <20240613234119.5ee92044@windsurf> (raw)
In-Reply-To: <20240514085801.3202503-1-thomas.petazzoni@bootlin.com>
Hello,
On Tue, 14 May 2024 10:58:00 +0200
Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> Our Bugzilla is so slow and unstable that it has become
> unusable. Let's switch to using the Gitlab issue tracker instead.
>
> There are still lots of references to the Bugzilla bug tracker in our
> News page at https://buildroot.org/news.html, but these are for older
> news.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
I was wondering if the other maintainers had any feedback on this patch?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-06-13 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 8:58 [Buildroot] [PATCH] docs, package/gcc: switch to Gitlab issue tracker Thomas Petazzoni via buildroot
2024-06-13 21:41 ` Thomas Petazzoni via buildroot [this message]
2024-06-13 21:56 ` Giulio Benetti
2024-06-15 8:08 ` Yann E. MORIN
2024-06-15 12:46 ` Thomas Petazzoni via buildroot
2024-06-15 14:30 ` Yann E. MORIN
2024-06-15 14:41 ` Peter Korsgaard
2024-06-15 14:41 ` Yann E. MORIN
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=20240613234119.5ee92044@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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