public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/rust/master] Merge #1672
Date: Mon,  5 Dec 2022 09:52:36 +0000 (GMT)	[thread overview]
Message-ID: <20221205095236.A04DE388883C@sourceware.org> (raw)

https://gcc.gnu.org/g:402118688f56d88d213572ee55a4245eec83b25f

commit 402118688f56d88d213572ee55a4245eec83b25f
Merge: 0bf68cf5e61 01fbbffcca6
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Sun Dec 4 14:58:48 2022 +0000

    Merge #1672
    
    1672: just for fun r=philberty a=philberty
    
    I love https://justforfunnoreally.dev/
    
    Co-authored-by: Philip Herron <philip.herron@embecosm.com>

Diff:

 README.md | 1 +
 1 file changed, 1 insertion(+)

                 reply	other threads:[~2022-12-05  9:52 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=20221205095236.A04DE388883C@sourceware.org \
    --to=tschwinge@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).