public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/omp/gcc-12] (5 commits) Merge branch 'releases/gcc-12' into devel/omp/gcc-12 Date: Thu, 2 Mar 2023 15:32:54 +0000 (GMT) [thread overview] Message-ID: <20230302153254.2EAD03858CDB@sourceware.org> (raw) The branch 'devel/omp/gcc-12' was updated to point to: 075e6e50266... Merge branch 'releases/gcc-12' into devel/omp/gcc-12 It previously pointed to: baa7f7adf75... Merge branch 'releases/gcc-12' into devel/omp/gcc-12 Diff: Summary of changes (added commits): ----------------------------------- 075e6e5... Merge branch 'releases/gcc-12' into devel/omp/gcc-12 b3f9d2c... Daily bump. (*) 15b6140... OpenMP/Fortran: Fix handling of optional is_device_ptr + bi 54fda48... Daily bump. (*) 6b14a8e... Daily bump. (*) (*) This commit already exists in another branch. Because the reference `refs/heads/devel/omp/gcc-12' matches your hooks.email-new-commits-only configuration, no separate email is sent for this commit.
next reply other threads:[~2023-03-02 15:32 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-02 15:32 Tobias Burnus [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-09-29 14:44 Tobias Burnus
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=20230302153254.2EAD03858CDB@sourceware.org \ --to=burnus@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: linkBe 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).