public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/aoliva/heads/testbase] (3 commits) [PR100127] Test for coroutine header in clang-compatible te
Date: Fri, 3 Mar 2023 12:37:29 +0000 (GMT) [thread overview]
Message-ID: <20230303123729.992BC3858D33@sourceware.org> (raw)
The branch 'aoliva/heads/testbase' was updated to point to:
1e4122f1159... [PR100127] Test for coroutine header in clang-compatible te
It previously pointed to:
dc1be3eb33c... testsuite: Tweak gcc.dg/attr-aligned.c for CRIS
Diff:
Summary of changes (added commits):
-----------------------------------
1e4122f... [PR100127] Test for coroutine header in clang-compatible te (*)
ddf7411... [vxworks] make wint_t and wchar_t the same distinct type (*)
2e8686c... [c++] suppress redundant null-addr warn in pfn from pmfn (*)
(*) This commit already exists in another branch.
Because the reference `refs/users/aoliva/heads/testbase' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
reply other threads:[~2023-03-03 12:37 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=20230303123729.992BC3858D33@sourceware.org \
--to=aoliva@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).