Re: [PATCH 2/2] MAINTAINERS: update new GRUB git repository and mailing list
Leo Sandoval via Grub-devel <[email protected]> Fri, 13 Mar 2026 09:15:37 -0600
| Newsgroups | org.gnu.grub-devel |
|---|---|
| Message-ID | <CACF7NThhCeSuW9R9sUDdqLz5YcfiXTiUO9hp8vL-YvO4rBzaFA@mail.gmail.com> |
--===============2178122377628732149== Content-Type: multipart/alternative; boundary="00000000000021f4e9064ce9587a" --00000000000021f4e9064ce9587a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Mar 13, 2026 at 6:39=E2=80=AFAM Neal Gompa <[email protected]> wro= te: > On Thu, Mar 12, 2026 at 2:02=E2=80=AFPM Leo Sandoval via Grub-devel > <[email protected]> wrote: > > > > > > > > On Thu, Mar 12, 2026 at 11:21=E2=80=AFAM Andrew Hamilton <adhamilt@gmai= l.com> > wrote: > >> > >> Will this info be updated on the > >> https://www.gnu.org/software/grub/ > >> site? > > > > > > Yes, that is the plan. In fact, not just the above but also these > > > > > > - ML https://www.gnu.org/software/grub/grub-mailinglist.html > > - Bugs https://savannah.gnu.org/bugs/?group=3Dgrub/ > > - lore https://lore.kernel.org/grub-devel/ > > > > These may take some time but volunteers are welcome to speed up the > process. > > > >> > >> Do you think this patch post will get the attention from all the key > users of Grub (like distribution maintainers, Buildroot, Yocto, etc.) to > start planning to update their build tools to point to a new place? > > > > > > I do not think so. > > > > What do you think is the best way to reach the outside > distro/buildroot/YP community? > > > > BTW, We will send an email soon with migration details as mentioned in > the commit description. > > > >> > >> > >> Will some pointer be left in place from the current Git and mailing > list to the new location, and archive of the current list for future > reference? > > > > > > Good points, I'm not sure of the best path but at least you pointed out > what is needed. Let me talk to the team about it. > > > > It should be possible to import the existing grub-devel mailing list > data into the fdo list instance, so that the history is preserved. I > recommend doing that. > Agree and that is the plan. We do not want to lose any bit from current mailing list. > > -- > =E7=9C=9F=E5=AE=9F=E3=81=AF=E3=81=84=E3=81=A4=E3=82=82=E4=B8=80=E3=81=A4= =EF=BC=81/ Always, there's only one truth! > > --00000000000021f4e9064ce9587a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g= mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Mar 13,= 2026 at 6:39=E2=80=AFAM Neal Gompa <<a href=3D"mailto:[email protected]= m">[email protected]</a>> wrote:<br></div><blockquote class=3D"gmail_qu= ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20= 4);padding-left:1ex">On Thu, Mar 12, 2026 at 2:02=E2=80=AFPM Leo Sandoval v= ia Grub-devel<br> <<a href=3D"mailto:[email protected]" target=3D"_blank">grub-devel@gnu.= org</a>> wrote:<br> ><br> ><br> ><br> > On Thu, Mar 12, 2026 at 11:21=E2=80=AFAM Andrew Hamilton <<a href= =3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>>= wrote:<br> >><br> >> Will this info be updated on the<br> >> <a href=3D"https://www.gnu.org/software/grub/" rel=3D"noreferrer" = target=3D"_blank">https://www.gnu.org/software/grub/</a><br> >>=C2=A0 site?<br> ><br> ><br> > Yes, that is the plan. In fact, not just the above but also these<br> ><br> ><br> > - ML <a href=3D"https://www.gnu.org/software/grub/grub-mailinglist.htm= l" rel=3D"noreferrer" target=3D"_blank">https://www.gnu.org/software/grub/g= rub-mailinglist.html</a><br> > - Bugs <a href=3D"https://savannah.gnu.org/bugs/?group=3Dgrub/" rel=3D= "noreferrer" target=3D"_blank">https://savannah.gnu.org/bugs/?group=3Dgrub/= </a><br> > - lore <a href=3D"https://lore.kernel.org/grub-devel/" rel=3D"noreferr= er" target=3D"_blank">https://lore.kernel.org/grub-devel/</a><br> ><br> > These may take some time but volunteers are welcome to speed up the pr= ocess.<br> ><br> >><br> >> Do you think this patch post will get the attention from all the k= ey users of Grub (like distribution maintainers, Buildroot, Yocto, etc.) to= start planning to update their build tools to point to a new place?<br> ><br> ><br> > I do not think so.<br> ><br> > What do you think is the best way to reach the outside distro/buildroo= t/YP community?<br> ><br> > BTW, We will send an email soon with migration details as mentioned in= the commit description.<br> ><br> >><br> >><br> >> Will some pointer be left in place from the current Git and mailin= g list to the new location, and archive of the current list for future refe= rence?<br> ><br> ><br> > Good points, I'm not sure of the best path but at least you pointe= d out what is needed. Let me talk to the team about it.<br> ><br> <br> It should be possible to import the existing grub-devel mailing list<br> data into the fdo list instance, so that the history is preserved. I<br> recommend doing that.<br></blockquote><div><br></div><div>Agree and that is= the plan. We do not want to lose any bit from current mailing list.</div><= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex"> <br> -- <br> =E7=9C=9F=E5=AE=9F=E3=81=AF=E3=81=84=E3=81=A4=E3=82=82=E4=B8=80=E3=81=A4=EF= =BC=81/ Always, there's only one truth!<br> <br> </blockquote></div></div> --00000000000021f4e9064ce9587a-- --===============2178122377628732149== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KR3J1Yi1kZXZl bCBtYWlsaW5nIGxpc3QKR3J1Yi1kZXZlbEBnbnUub3JnCmh0dHBzOi8vbGlzdHMuZ251Lm9yZy9t YWlsbWFuL2xpc3RpbmZvL2dydWItZGV2ZWwK --===============2178122377628732149==--