Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Romain Naour <romain.naour@gmail.com>,
	Buildroot List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] docs, package/gcc: switch to Gitlab issue tracker
Date: Sat, 15 Jun 2024 16:41:28 +0200	[thread overview]
Message-ID: <Zm2oGClDG0FqqZPf@landeda> (raw)
In-Reply-To: <20240514085801.3202503-1-thomas.petazzoni@bootlin.com>

Thomas, All,

On 2024-05-14 10:58 +0200, Thomas Petazzoni via buildroot spake thusly:
> 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>
[--SNIP--]
> diff --git a/docs/website/support.html b/docs/website/support.html
> index 28873c6d76..75551b770e 100644
> --- a/docs/website/support.html
> +++ b/docs/website/support.html
> @@ -80,8 +80,9 @@
>  		  <img class="img-responsive" src="images/bug-buddy.png" style="max-width:50px; margin-bottom:10px;">
>  		</div>
>  		<div class="col-sm-11">
> -		  <p>If you think you found a bug in Buildroot, you can use the
> -		    <a href="https://bugs.buildroot.org/">Bug Tracker</a> to post your bugs and/or
> +		  <p>If you think you found a bug in Buildroot, you
> +		  can use the

Spurious reflow; I dropped it.

Applied to master, thanks.

As planned with your non-plan, I'm planning on planing out old bug
tracker, and closing still-opened issues.

Still, it would be nice if we could get an issue template for new issues
that will be opened in our shinny new bug tracker.

Regards,
Yann E. MORIN.

> +		    <a href="https://gitlab.com/buildroot.org/buildroot/-/issues">Bug Tracker</a> to post your bugs and/or
>  		    participate to find solutions to existing problems.</p>
>  
>  		  <p>Note: patches are only accepted through the mailing list.</p>
> diff --git a/package/gcc/gcc.mk b/package/gcc/gcc.mk
> index 672f9472a9..e4780353cb 100644
> --- a/package/gcc/gcc.mk
> +++ b/package/gcc/gcc.mk
> @@ -83,7 +83,7 @@ HOST_GCC_COMMON_CONF_OPTS = \
>  	--with-mpc=$(HOST_DIR) \
>  	--with-mpfr=$(HOST_DIR) \
>  	--with-pkgversion="Buildroot $(BR2_VERSION_FULL)" \
> -	--with-bugurl="http://bugs.buildroot.net/" \
> +	--with-bugurl="https://gitlab.com/buildroot.org/buildroot/-/issues" \
>  	--without-zstd
>  
>  ifeq ($(BR2_REPRODUCIBLE),y)
> -- 
> 2.45.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-06-15 14: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
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 [this message]

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=Zm2oGClDG0FqqZPf@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.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