public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/meissner/heads/work140-vsubreg] (3 commits) Merge commit 'refs/users/meissner/heads/work140-vsubreg' of
Date: Fri, 20 Oct 2023 18:39:28 +0000 (GMT)	[thread overview]
Message-ID: <20231020183928.5465A385C6E7@sourceware.org> (raw)

The branch 'meissner/heads/work140-vsubreg' was updated to point to:

 c71dffcd6168... Merge commit 'refs/users/meissner/heads/work140-vsubreg' of

It previously pointed to:

 965cc31fc610... Add ChangeLog.vsubreg and update REVISION.

Diff:

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

  c71dffc... Merge commit 'refs/users/meissner/heads/work140-vsubreg' of
  02ff599... Add ChangeLog.vsubreg and update REVISION.
  d6c5b21... Power10: Add options to disable load and store vector pair. (*)

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

                 reply	other threads:[~2023-10-20 18:39 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=20231020183928.5465A385C6E7@sourceware.org \
    --to=meissner@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).