public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: [GOLDSTAR] Re: [ITP] autoconf2.7
Date: Fri, 3 Dec 2021 17:14:59 +0100	[thread overview]
Message-ID: <YapCg1QCMHDKhedj@calimero.vinschen.de> (raw)
In-Reply-To: <87h7bpdcum.fsf@Otto.invalid>

On Dec  3 14:42, ASSI wrote:
> Corinna Vinschen writes:
> > Since Fedora did basically the same, as Ken pointed out, maybe we're
> > a bit meticulous if we create a new package for 2.7x?
> 
> Well, if we don't, we're SOL if we hit an incompatibility that the Linux
> folks don't need to care about…  that was why I originally suggested to
> wait it out a bit.
> 
> > I don't know how  the experience is in the various environments, but
> > nobody appears to care...
> 
> If I look at the changes, many are for "fringe" platforms, so how far
> out in the fringes is Cygwin?

No idea.  I cringe at the idea of calling Cygwin a fringe platform.
Now, if you call Cygwin a Gringe platform OTOH :)

Nah, in fact, given we already have the autoconf versioning in place,
it probably doesn't hurt to do it right.

Btw., goldstar request for Achim here!


Corinna

  reply	other threads:[~2021-12-03 16:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 19:51 Achim Gratz
2021-12-02 20:24 ` Marco Atzeri
2021-12-02 20:45   ` Achim Gratz
2021-12-02 21:36     ` Marco Atzeri
2021-12-04 12:33     ` Achim Gratz
2021-12-04 13:02       ` Marco Atzeri
2021-12-02 20:26 ` Ken Brown
2021-12-03 10:22   ` ASSI
2021-12-03 11:59     ` Corinna Vinschen
2021-12-03 13:42       ` ASSI
2021-12-03 16:14         ` Corinna Vinschen [this message]
2021-12-03 20:40     ` Achim Gratz
2021-12-08 18:46       ` Achim Gratz
2021-12-09 10:24         ` Corinna Vinschen
2021-12-09 16:11           ` Ken Brown
2021-12-09 18:30             ` Achim Gratz
2021-12-03 20:47 ` Achim Gratz

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=YapCg1QCMHDKhedj@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-apps@cygwin.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).