home.social

Search

1000 results for “sourceware”

  1. On Friday, November 17th 2023 at 13:00 UTC the switches in the Red Hat community cage will see an upgrade and reboot.

    This might impact connectivity of #sourceware gcc.gnu.org valgrind.org cygwin.org elfutils.org dwarfstd.org

    All 1g ports will be not switching data and will be down from about 13:00 to no later than 13:30 UTC.

  2. On Friday, November 17th 2023 at 13:00 UTC the switches in the Red Hat community cage will see an upgrade and reboot.

    This might impact connectivity of gcc.gnu.org valgrind.org cygwin.org elfutils.org dwarfstd.org

    All 1g ports will be not switching data and will be down from about 13:00 to no later than 13:30 UTC.

  3. On Friday, November 17th 2023 at 13:00 UTC the switches in the Red Hat community cage will see an upgrade and reboot.

    This might impact connectivity of #sourceware gcc.gnu.org valgrind.org cygwin.org elfutils.org dwarfstd.org

    All 1g ports will be not switching data and will be down from about 13:00 to no later than 13:30 UTC.

  4. On Friday, November 17th 2023 at 13:00 UTC the switches in the Red Hat community cage will see an upgrade and reboot.

    This might impact connectivity of #sourceware gcc.gnu.org valgrind.org cygwin.org elfutils.org dwarfstd.org

    All 1g ports will be not switching data and will be down from about 13:00 to no later than 13:30 UTC.

  5. @sourceware thanks to #FUTO futo.org for doubling the (micro) grant, originally just for #Valgrind, to maintain and expand the #Sourceware infrastructure for all core toolchain and developer tool projects.

    If you also want to donate to Sourceware please see sfconservancy.org/donate and become a @conservancy Sustainer or give directly by mentioning Sourceware as comment or on the memo line.

  6. @sourceware thanks to futo.org for doubling the (micro) grant, originally just for , to maintain and expand the infrastructure for all core toolchain and developer tool projects.

    If you also want to donate to Sourceware please see sfconservancy.org/donate and become a @conservancy Sustainer or give directly by mentioning Sourceware as comment or on the memo line.

  7. @sourceware thanks to #FUTO futo.org for doubling the (micro) grant, originally just for #Valgrind, to maintain and expand the #Sourceware infrastructure for all core toolchain and developer tool projects.

    If you also want to donate to Sourceware please see sfconservancy.org/donate and become a @conservancy Sustainer or give directly by mentioning Sourceware as comment or on the memo line.

  8. @sourceware thanks to #FUTO futo.org for doubling the (micro) grant, originally just for #Valgrind, to maintain and expand the #Sourceware infrastructure for all core toolchain and developer tool projects.

    If you also want to donate to Sourceware please see sfconservancy.org/donate and become a @conservancy Sustainer or give directly by mentioning Sourceware as comment or on the memo line.

  9. @sourceware thanks to #FUTO futo.org for doubling the (micro) grant, originally just for #Valgrind, to maintain and expand the #Sourceware infrastructure for all core toolchain and developer tool projects.

    If you also want to donate to Sourceware please see sfconservancy.org/donate and become a @conservancy Sustainer or give directly by mentioning Sourceware as comment or on the memo line.

  10. updates. email ARC headers, @osuosl provides a big arm64 server for builder.sourceware.org and patchwork updates.

    inbox.sourceware.org/overseers

  11. If you enjoyed the GNU Tools Cauldron and like to organize an online virtual mini-BoF followup around some topic or project then the @conservancy BBB server is available for all #Sourceware projects.

    inbox.sourceware.org/9ca90cd01

  12. If you enjoyed the GNU Tools Cauldron and like to organize an online virtual mini-BoF followup around some topic or project then the @conservancy BBB server is available for all projects.

    inbox.sourceware.org/9ca90cd01

  13. If you enjoyed the GNU Tools Cauldron and like to organize an online virtual mini-BoF followup around some topic or project then the @conservancy BBB server is available for all #Sourceware projects.

    inbox.sourceware.org/9ca90cd01

  14. If you enjoyed the GNU Tools Cauldron and like to organize an online virtual mini-BoF followup around some topic or project then the @conservancy BBB server is available for all #Sourceware projects.

    inbox.sourceware.org/9ca90cd01

  15. Looking forward to the GNU Tools Cauldron in Cambridge at the end of this week.

    gcc.gnu.org/wiki/cauldron2023

    #Sourceware Project Leadership Committee members @ezannoni
    @iank and @mjw will be there. Joined by Bradley Kuhn the Policy Fellow of our fiscal sponsor @conservancy

    Happy to discuss any Sourceware, GNU Toolchain Infrastructure issues and our 25 year Roadmap.

    sourceware.org/sourceware-25-r

  16. Looking forward to the GNU Tools Cauldron in Cambridge at the end of this week.

    gcc.gnu.org/wiki/cauldron2023

    Project Leadership Committee members @ezannoni
    @iank and @mjw will be there. Joined by Bradley Kuhn the Policy Fellow of our fiscal sponsor @conservancy

    Happy to discuss any Sourceware, GNU Toolchain Infrastructure issues and our 25 year Roadmap.

    sourceware.org/sourceware-25-r

  17. Looking forward to the GNU Tools Cauldron in Cambridge at the end of this week.

    gcc.gnu.org/wiki/cauldron2023

    #Sourceware Project Leadership Committee members @ezannoni
    @iank and @mjw will be there. Joined by Bradley Kuhn the Policy Fellow of our fiscal sponsor @conservancy

    Happy to discuss any Sourceware, GNU Toolchain Infrastructure issues and our 25 year Roadmap.

    sourceware.org/sourceware-25-r

  18. Looking forward to the GNU Tools Cauldron in Cambridge at the end of this week.

    gcc.gnu.org/wiki/cauldron2023

    #Sourceware Project Leadership Committee members @ezannoni
    @iank and @mjw will be there. Joined by Bradley Kuhn the Policy Fellow of our fiscal sponsor @conservancy

    Happy to discuss any Sourceware, GNU Toolchain Infrastructure issues and our 25 year Roadmap.

    sourceware.org/sourceware-25-r

  19. Because of dkim, strict dmarc policies and an old mailman setup Sourceware mailinglists used From rewriting.

    No more! We upgraded mailman, gave up subject prefixes, mail footers, html stripping and reply-to mangling.

    The #glibc libc-alpha list is the first to try it out.

    We'll evaluate how well this works at our next Open Office hour (this Friday) and whether to recommend it to other #Sourceware projects.

    Thanks to the FSF tech-team for walking us through their setup for lists.gnu.org

  20. Uncover interesting test cases with AI/ML and on

    developers.redhat.com/articles

    The AI/ML engine is already running on our showcase sourceware.org server. The AI/ML predictions are shown on the panels, highlighting "mismatches"

    builder.sourceware.org/testruns

  21. HTML email. Most projects allow it, if there is at least a text/plain alternative.

    But is not so forgiving, it only allows plain-text emails, HTML is rejected by default.

    So the inbox.sourceware.org archive was incomplete.

    We now have a filter that removes redundant HTML parts before storing in public-inbox. And we re-imported missing emails to make the archive complete.

    But please don't sent HTML email. It will make DKIM verification of your email impossible.

  22. Uncover interesting test cases with AI/ML and #Bunsen on #Sourceware

    developers.redhat.com/articles

    The AI/ML engine is already running on our showcase sourceware.org server. The AI/ML predictions are shown on the #DejaGnu panels, highlighting "mismatches"

    builder.sourceware.org/testrun

  23. After the #glibc libc-alpha and #gcc gcc-patches mailinglist tests to avoid From rewriting worked out nicely we enabled the same settings to some other mailinglists.

    The other gcc patches lists for #libstdc++, #libgccjit, #fortran and #gcc-rust. And those project that use #patchwork, #newlib, #elfutils, #libabigail and #gdb.

    This hopefully makes mailing patches and using git am on them a bit nicer.

    Please contact us if you have any issues with the mailinglists.
    sourceware.org/mission.html#or

  24. After the #glibc libc-alpha and #gcc gcc-patches mailinglist tests to avoid From rewriting worked out nicely we enabled the same settings to some other mailinglists.

    The other gcc patches lists for #libstdc++, #libgccjit, #fortran and #gcc-rust. And those project that use #patchwork, #newlib, #elfutils, #libabigail and #gdb.

    This hopefully makes mailing patches and using git am on them a bit nicer.

    Please contact us if you have any issues with the mailinglists.
    sourceware.org/mission.html#or

  25. After the #glibc libc-alpha and #gcc gcc-patches mailinglist tests to avoid From rewriting worked out nicely we enabled the same settings to some other mailinglists.

    The other gcc patches lists for #libstdc++, #libgccjit, #fortran and #gcc-rust. And those project that use #patchwork, #newlib, #elfutils, #libabigail and #gdb.

    This hopefully makes mailing patches and using git am on them a bit nicer.

    Please contact us if you have any issues with the mailinglists.
    sourceware.org/mission.html#or

  26. After the #glibc libc-alpha and #gcc gcc-patches mailinglist tests to avoid From rewriting worked out nicely we enabled the same settings to some other mailinglists.

    The other gcc patches lists for #libstdc++, #libgccjit, #fortran and #gcc-rust. And those project that use #patchwork, #newlib, #elfutils, #libabigail and #gdb.

    This hopefully makes mailing patches and using git am on them a bit nicer.

    Please contact us if you have any issues with the mailinglists.
    sourceware.org/mission.html#or

  27. Because of dkim, strict dmarc policies and an old mailman setup Sourceware mailinglists used From rewriting.

    No more! We upgraded mailman, gave up subject prefixes, mail footers, html stripping and reply-to mangling.

    The libc-alpha list is the first to try it out.

    We'll evaluate how well this works at our next Open Office hour (this Friday) and whether to recommend it to other projects.

    Thanks to the FSF tech-team for walking us through their setup for lists.gnu.org