config-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Rethinking configuration tuples


From: John Ericson
Subject: Re: Rethinking configuration tuples
Date: Thu, 14 Sep 2023 00:55:06 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0

OK here we go:

  1. https://github.com/ericson2314/gnu-config/commit/windows-mingnu.patch
  2. https://github.com/ericson2314/gnu-config/commit/windows-mingw.patch
  3. https://github.com/ericson2314/gnu-config/commit/no-windows-gnu.patch

I tried to honestly argue for each of them the best I could in the commit message. I know I prefer (1); I am guessing Jacob prefers (2), and Po Lu prefers (3).

Have fun, Dmitry :).

I suppose rather than just idly speculating on how nice it would be to standardize with LLVM, this might be a good time to actually post to their Discourse instance and solicit feedback. If anyone else agrees I will happily do so.

Cheers,

John

On 9/11/23 17:55, John Ericson wrote:
I can submit two patches (effectively amending my prior, landed patch) with options that I think people would prefer. Will do that shortly.

On 9/11/23 17:53, Dmitry V. Levin wrote:
Hi,

On Mon, Sep 11, 2023 at 10:11:39AM +0800, Po Lu wrote:
Where are the config maintainers?  Karl Barry and company?
(I don't remember his e-mail nor do I have it at hand.)

I would expect them to be actively reading this list, but instead my
original request has been left twisting in the wind.
I'm the maintainer and I'm actively reading this list now,
a bit surprised to find so many messages at this time of year. :)

Apparently, you don't quite like commit
91f6a7f616b161c25ba2001861a40e662e18c4ad that added
$cpu-$vendor-windows-{gnu,msvc} support to config.sub, but I'm not sure
I understood what exactly do you suggest to change in this case.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]