public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sergey Bugaev <bugaevc@gmail.com>
To: Thomas Schwinge <tschwinge@baylibre.com>
Cc: Richard Sandiford <richard.sandiford@arm.com>,
	gcc-patches@gcc.gnu.org, bug-hurd@gnu.org
Subject: Re: [PATCH gcc 1/3] Move GNU/Hurd startfile spec from config/i386/gnu.h to config/gnu.h
Date: Sat, 23 Mar 2024 17:38:51 +0300	[thread overview]
Message-ID: <CAN9u=Hf7QyRYBF+L47+Tf8i6aBrUkCJ9vPgkY2xbog7n=Rcsaw@mail.gmail.com> (raw)
In-Reply-To: <877chwpv5m.fsf@euler.schwinge.ddns.net>

On Wed, Mar 20, 2024 at 10:20 PM Thomas Schwinge <tschwinge@baylibre.com> wrote:
> Hi!

Hi Thomas,

> Sergey, great work on aarch64 GNU/Hurd!  (... where these GCC bits
> clearly were the less complicated part...)  ;-)

thanks! (and indeed they were :)

> Please re-submit with ChangeLog updates added to the Git commit logs; see
> <https://gcc.gnu.org/contribute.html#patches> ->
> <https://gcc.gnu.org/codingconventions.html#ChangeLogs>, and/or 'git log'
> for guidance.  You may use
> 'contrib/gcc-changelog/git_check_commit.py --print-changelog' to verify.

Done so, and git_check_commit.py seems happy with my attempt. I
rebased (fixing a trivial merge conflict) and posted v2, please take a
look.

Sergey

  reply	other threads:[~2024-03-23 14:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-01 11:53 Sergey Bugaev
2024-01-01 11:53 ` [PATCH gcc 2/3] aarch64: Add support for aarch64-gnu (GNU/Hurd on AArch64) Sergey Bugaev
2024-01-01 11:53 ` [PATCH gcc 3/3] libgcc: Add basic " Sergey Bugaev
2024-01-03  9:49 ` [PATCH gcc 1/3] Move GNU/Hurd startfile spec from config/i386/gnu.h to config/gnu.h Richard Sandiford
2024-03-20 19:20   ` Thomas Schwinge
2024-03-23 14:38     ` Sergey Bugaev [this message]
2024-03-23 14:35 ` [PATCH v2 " Sergey Bugaev
2024-03-23 14:35   ` [PATCH v2 2/3] aarch64: Add support for aarch64-gnu (GNU/Hurd on AArch64) Sergey Bugaev
2024-04-02 17:26     ` Richard Sandiford
2024-04-05 12:13       ` Sergey Bugaev
2024-04-09  7:27         ` Thomas Schwinge
2024-04-09  8:04           ` Sergey Bugaev
2024-04-09 16:24             ` Palmer Dabbelt
2024-04-09 16:57               ` Sergey Bugaev
2024-04-10  0:04                 ` Palmer Dabbelt
2024-04-10  7:12               ` Regeneration of 'gcc/config/riscv/riscv.opt.urls' (was: [PATCH v2 2/3] aarch64: Add support for aarch64-gnu (GNU/Hurd on AArch64)) Thomas Schwinge
2024-03-23 14:35   ` [PATCH v2 3/3] libgcc: Add basic support for aarch64-gnu (GNU/Hurd on AArch64) Sergey Bugaev

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='CAN9u=Hf7QyRYBF+L47+Tf8i6aBrUkCJ9vPgkY2xbog7n=Rcsaw@mail.gmail.com' \
    --to=bugaevc@gmail.com \
    --cc=bug-hurd@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.sandiford@arm.com \
    --cc=tschwinge@baylibre.com \
    /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).