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: Mon, 14 Jun 2021 13:38:16 +0000 (GMT)	[thread overview]
Message-ID: <20210614133816.43746388A811@sourceware.org> (raw)

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

 1775bce3a2c... Merge branch 'master' into devel/sphinx

It previously pointed to:

 c0f8bdc00d1... Remove @ref.

Diff:

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

  1775bce... Merge branch 'master' into devel/sphinx
  f389f2a... docs: remove extra '+' character in option listing. (*)
  45fb3d4... libstdc++: Add explicit -std=gnu++17 option to test (*)
  b76a529... libstdc++: Implement LWG 3465 for std::compare_partial_orde (*)
  e2c79b9... libstdc++: Change [cmp.alg] assertions to constraints (*)
  a893b26... Fortran: resolve.c - remove '*XCNEW' based nullifying (*)
  c4c47a8... arc: Add --with-fpu support for ARCv2 cpus (*)
  831589c... Do not check if SMS succeeds on powerpc (*)
  917efba... libstdc++: Use reserved name for attribute [PR101055] (*)

(*) 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:[~2021-06-14 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 13:38 Martin Liska [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-20 15:24 Martin Liska
2021-08-23 13:42 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=20210614133816.43746388A811@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).