public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: Re: [PATCH] libgloss: wince: update to automake-1.15
Date: Tue, 21 Dec 2021 20:43:40 -0500	[thread overview]
Message-ID: <YcKCzCRt/a20HD7Z@vapier> (raw)
In-Reply-To: <c186aaf2-be72-c89e-d151-57c4738522d9@SystematicSw.ab.ca>

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

On 21 Dec 2021 11:19, Brian Inglis wrote:
> On 2021-12-21 02:19, Corinna Vinschen wrote:
> > On Dec 21 01:28, Mike Frysinger wrote:
> >> On 08 Nov 2021 11:06, Corinna Vinschen wrote:
> >>> On Nov  6 20:30, Mike Frysinger wrote:
> >>>> Drop the cygnus options and migrate to current versions of autotools.
> >>>> ---
> >>>> NB: I haven't been able to compile test this because current binutils
> >>>> fails to build for wince targets.
> >>>
> >>> Can anybode else here test it, please?
> >>
> >> should we just merge & wait for feedback ?
> > 
> > Yes, sounds like a plan.
> 
> Maybe wait until after New Year, unless you are all going to be online 
> monitoring for wails of anguish, instead of enjoying wassails ;^>

i assume you mean "wait until after the yearly release of newlib which is
normally cut in Dec" ?  i don't think there's a good/bad time for general
merging into git & waiting for feedback via that.

i'm fine waiting until the next newlib version is cut.  might be good to
do it before the cygnus cleanups are merged too.
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2021-12-22  1:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-07  0:30 Mike Frysinger
2021-11-08 10:06 ` Corinna Vinschen
2021-12-21  6:28   ` Mike Frysinger
2021-12-21  9:19     ` Corinna Vinschen
2021-12-21 18:19       ` Brian Inglis
2021-12-22  1:43         ` Mike Frysinger [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=YcKCzCRt/a20HD7Z@vapier \
    --to=vapier@gentoo.org \
    --cc=newlib@sourceware.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).