public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Iain Buclaw <ibuclaw@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/ibuclaw/heads/mingw] (7 commits) Initial Mingw/MSVC support
Date: Mon, 19 Apr 2021 18:02:51 +0000 (GMT)	[thread overview]
Message-ID: <20210419180251.B44943947411@sourceware.org> (raw)

The branch 'ibuclaw/heads/mingw' was updated to point to:

 84d266ebccc... Initial Mingw/MSVC support

It previously pointed to:

 35933da6a1a... Initial Mingw/MSVC support

Diff:

!!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST):
-------------------------------------------------------------------

  35933da... Initial Mingw/MSVC support
  acf8e40... Sync druntime
  1cadae9... libphobos: Add Thread/Fiber support code for Darwin
  890e392... libphobos: Add D runtime support code for MinGW
  cf73e5a... libphobos: Add section support code for OpenBSD


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

  84d266e... Initial Mingw/MSVC support
  dc7d1c7... d: Fix ICE in when formating a string with '%' or '`' chara (*)
  e19c638... libphobos: Merge upstream druntime 89f870b7, phobos e6907ff (*)
  6eae754... libphobos: Add Thread/Fiber support code for Darwin (PR9805 (*)
  b66e72b... libphobos: Add D runtime support code for MinGW (PR99794) (*)
  d86e608... libphobos: Add section support code for OpenBSD (PR99691) (*)
  3bffc4b... arm: partial revert of r11-8168 [PR100067] (*)

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


                 reply	other threads:[~2021-04-19 18:02 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=20210419180251.B44943947411@sourceware.org \
    --to=ibuclaw@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).