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/devel/sphinx] (9 commits) Merge branch 'master' into devel/sphinx
Date: Tue, 20 Sep 2022 15:24:34 +0000 (GMT)	[thread overview]
Message-ID: <20220920152434.CF4DF38582B2@sourceware.org> (raw)

The branch 'devel/sphinx' was updated to point to:

 c9c59aa19c0... Merge branch 'master' into devel/sphinx

It previously pointed to:

 9934c1e645a... Merge branch 'master' into devel/sphinx

Diff:

Summary of changes (added commits):
-----------------------------------

  c9c59aa... Merge branch 'master' into devel/sphinx
  d812e8c... fortran: add link to ISO_VARYING_STRING module [PR106636] (*)
  6bf5a70... aarch64: Fix GTY markup for arm_sve.h [PR106491] (*)
  1005c89... vect: Fix SLP layout handling of masked loads [PR106794] (*)
  4a773bf... vect: Fix missed gather load opportunity (*)
  3e41e69... [PR106970] New test for PR that has already been fixed. (*)
  84b2ab9... c++: stream PACK_EXPANSION_EXTRA_ARGS [PR106761] (*)
  a8bb495... replace "the the" typos (*)
  5ed0c11... libstdc++: Fix typo in <cstdlib> for freestanding (*)

(*) This commit already exists in another branch.
    Because the reference `refs/heads/devel/sphinx' matches
    your hooks.email-new-commits-only configuration,
    no separate email is sent for this commit.

             reply	other threads:[~2022-09-20 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 15:24 Martin Liska [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-23 13:42 Martin Liska
2021-06-14 13:38 Martin Liska
2021-06-02 12:46 Martin Liska

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=20220920152434.CF4DF38582B2@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).