public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/rust/master] Merge #1698
Date: Tue,  7 Feb 2023 17:54:29 +0000 (GMT)	[thread overview]
Message-ID: <20230207175429.AF03F3858C66@sourceware.org> (raw)

https://gcc.gnu.org/g:278f7616efc85988ee777f7b244ce65f758f0301

commit 278f7616efc85988ee777f7b244ce65f758f0301
Merge: 1f96413438d d10d3dc997b
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Fri Feb 3 13:28:26 2023 +0000

    Merge #1698
    
    1698: update the ubuntu version r=CohenArthur a=ArshErgon
    
    Fixes: #1689
    updated the ubuntu-version from 20.04 to 22.04
    
    Thank you for making Rust GCC better!
    
    If your PR fixes an issue, you can add "Fixes #issue_number" into this
    PR description and the git commit message. This way the issue will be
    automatically closed when your PR is merged. If your change addresses
    an issue but does not fully fix it please mark it as "Addresses #issue_number"
    in the git commit message.
    
    Here is a checklist to help you with your PR.
    
    - \[ ] GCC development requires copyright assignment or the Developer's Certificate of Origin sign-off, see https://gcc.gnu.org/contribute.html or https://gcc.gnu.org/dco.html
    - \[ ] Read contributing guidlines
    - \[ ] `make check-rust` passes locally
    - \[ ] Run `clang-format`
    - \[ ] Added any relevant test cases to `gcc/testsuite/rust/`
    
    Note that you can skip the above if you are just opening a WIP PR in
    order to get feedback.
    ---
    
    *Please write a comment explaining your change. This is the message
    that will be part of the merge commit.
    
    
    Co-authored-by: ArshErgon <arshergon@gmail.com>

Diff:

 .github/bors_log_expected_warnings | 196 +++++++++++--------------------------
 .github/workflows/bootstrap.yml    |   2 +-
 .github/workflows/ccpp.yml         |   4 +-
 3 files changed, 61 insertions(+), 141 deletions(-)

                 reply	other threads:[~2023-02-07 17:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230207175429.AF03F3858C66@sourceware.org \
    --to=tschwinge@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).