public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/marxin/heads/merge-libsanitizer-v7] (8 commits) asan: update expected format based on ASAN
Date: Tue, 15 Nov 2022 14:44:55 +0000 (GMT) [thread overview]
Message-ID: <20221115144455.8291338983A8@sourceware.org> (raw)
The branch 'marxin/heads/merge-libsanitizer-v7' was updated to point to:
bf64e942b92... asan: update expected format based on ASAN
It previously pointed to:
b9da933ec88... asan: update expected format based on ASAN
Diff:
!!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST):
-------------------------------------------------------------------
b9da933... asan: update expected format based on ASAN
ddfa73a... libsanitizer: Apply local patches
725fff7... libsanitizer: merge from upstream ae59131d3ef311fb4b1e50627
Summary of changes (added commits):
-----------------------------------
bf64e94... asan: update expected format based on ASAN
16942e5... libsanitizer: Apply local patches
47538f1... libsanitizer: merge from upstream ae59131d3ef311fb4b1e50627
3895318... libsanitizer: use git clone --depth 1 (*)
fe26b04... Revert "docs: Fix expected diagnostics URL [PR107599]" (*)
d34dea0... libstdc++: Document use of Markdown for Doxygen comments (*)
f5f2686... doc: Format region pragmas as separate items (*)
dd32062... ira: Remove duplicate `memset' over `full_costs' from `assi (*)
(*) This commit already exists in another branch.
Because the reference `refs/users/marxin/heads/merge-libsanitizer-v7' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
reply other threads:[~2022-11-15 14:44 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=20221115144455.8291338983A8@sourceware.org \
--to=marxin@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).