public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lorenzo Salvadore <developer@lorenzosalvadore.it>
To: Iain Buclaw <ibuclaw@gdcproject.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	"andreast@gcc.gnu.org" <andreast@gcc.gnu.org>,
	Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: Ping^3: [PATCH] d: Update __FreeBSD_version values [PR107469]
Date: Sat, 28 Jan 2023 08:48:57 +0000	[thread overview]
Message-ID: <k3Uo7I0zA2VdidQxd9eZaq_xp-W7puEmtS6GRbVJf0SyG90H-qF1TPHQ3vI0mCC9ZCyDnMPXsSBirrJaU5Vgjlha2mNcyHtbeOOzK2HtnsE=@lorenzosalvadore.it> (raw)
In-Reply-To: <1674484997.yjxgki5kqd.astroid@pulse.none>

------- Original Message -------
On Monday, January 23rd, 2023 at 3:45 PM, Iain Buclaw <ibuclaw@gdcproject.org> wrote:


> 
> 
> Excerpts from Lorenzo Salvadore's message of Januar 10, 2023 5:10 pm:
> 
> > Hello,
> > 
> > Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605685.html
> > 
> > I would like to remind that Gerald Pfeifer already volunteered to commit this patch
> > when it is approved. However the patch has not been approved yet.
> 
> 
> Hi, sorry for belated reply.
> 
> Yes is fine for now, I'm concerned that it'll just be the same again
> come FreeBSD 15, 16, 17...
> 
> There needs to be a better mechanism to determine which FreeBSD version
> is being compiled for, but that shouldn't block this going in.
> 
> OK.

Thanks, I will keep this concern in mind when FreeBSD 15 starts its
development and then I will try to submit a patch proposing a better
mechanism.

Cheers,

Lorenzo Salvadore

      reply	other threads:[~2023-01-28  8:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 23:07 Lorenzo Salvadore
2022-11-27  8:23 ` Ping: " Lorenzo Salvadore
2022-12-14 13:55   ` Ping^2: " Lorenzo Salvadore
2022-12-24  0:10     ` Gerald Pfeifer
2023-01-10 16:10     ` Ping^3: " Lorenzo Salvadore
2023-01-23 14:45       ` Iain Buclaw
2023-01-28  8:48         ` Lorenzo Salvadore [this message]

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='k3Uo7I0zA2VdidQxd9eZaq_xp-W7puEmtS6GRbVJf0SyG90H-qF1TPHQ3vI0mCC9ZCyDnMPXsSBirrJaU5Vgjlha2mNcyHtbeOOzK2HtnsE=@lorenzosalvadore.it' \
    --to=developer@lorenzosalvadore.it \
    --cc=andreast@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=ibuclaw@gdcproject.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).