All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Rainbolt <arraybolt3@gmail.com>
To: mlewando@redhat.com
Cc: grub-devel@gnu.org
Subject: Re: GRUB repository moved to freedesktop
Date: Fri, 27 Mar 2026 01:29:44 -0400	[thread overview]
Message-ID: <20260327012759.21b09e38@gmail.com> (raw)
In-Reply-To: CA+tGYp7ijT6xv_ufj1vcDfjATSnGu9Q9tM+B4SJg9+A1WQbqGg@mail.gmail.com


[-- Attachment #1.1: Type: text/plain, Size: 678 bytes --]

> Effective immediately, you can open MRs on gitlab instead of sending
> patches here. We will continue to monitor this list for about a
> month, but encourage all GRUB contributors to use the new workflow
> instead.

Has the bug tracker moved to Freedesktop's GitLab as well, or should
mailing lists still be used for that? I assumed the bug tracker was the
right place now because "work items" weren't disabled, so I just used
the GitLab bugtracker a bit ago to file a bug/feature request that I
intend on implementing [1]. I'm not sure if that's where I should have
posted it though.

--
Aaron

[1] https://gitlab.freedesktop.org/gnu-grub/grub/-/work_items/4

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

             reply	other threads:[~2026-03-27  5:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27  5:29 Aaron Rainbolt [this message]
2026-03-27  8:42 ` GRUB repository moved to freedesktop Marta Lewandowska via Grub-devel
2026-03-27 12:31 ` Neal Gompa
  -- strict thread matches above, loose matches on Subject: below --
2026-03-13 18:59 Marta Lewandowska via Grub-devel

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=20260327012759.21b09e38@gmail.com \
    --to=arraybolt3@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=mlewando@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.