From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: glibc 2.27: 3 weeks till release
Date: Mon, 22 Jan 2018 23:58:00 -0000 [thread overview]
Message-ID: <1747850650.411713.1516665503888@poczta.nazwa.pl> (raw)
In-Reply-To: <alpine.DEB.2.20.1801121710580.2172@digraph.polyomino.org.uk>
12.01.2018 18:14 Joseph Myers <joseph@codesourcery.com> wrote:
>
>
> On Fri, 12 Jan 2018, Rafal Luzynski wrote:
>
> > > What's the impact on statically linked applications? Will they continue
> > > to be able to read both kinds of locale data?
> >
> > I have not tried this so I don't know, I assume they will not be able.
> >
> > Is it likely that an application linked statically against the new glibc
> > will read the old locale data and there will be no chance to rebuild
> > them from sources, or vice versa? Note that the old locale data sources
> > are valid, the new features are optional.
>
> We've previously accepted some incompatibility of compiled locale files
> with old glibc versions (and thus old statically linked binaries). Note
> the following in the NEWS file for 2.19:
>
> [ ...cut to save the space... ]
>
> If the present change affects binary locale compatibility, such a note
> will be needed in the "Deprecated and removed features, and other changes
> affecting compatibility:" section of NEWS for 2.27.
I think that we still need this change in NEWS, don't we? Will anybody
please write and commit this? I have already proved that my English skills
are insufficient. :-(
Regards,
Rafal
next prev parent reply other threads:[~2018-01-22 23:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 3:44 Dmitry V. Levin
2018-01-11 5:10 ` Carlos O'Donell
2018-01-11 13:45 ` Joseph Myers
2018-01-11 14:42 ` Zack Weinberg
2018-01-11 14:46 ` Dmitry V. Levin
2018-01-11 14:51 ` Zack Weinberg
2018-01-11 14:57 ` Dmitry V. Levin
2018-01-11 15:14 ` Zack Weinberg
2018-01-11 16:03 ` Rafal Luzynski
2018-01-12 4:15 ` Carlos O'Donell
2018-01-12 7:47 ` Florian Weimer
2018-01-12 8:10 ` Rafal Luzynski
2018-01-12 17:15 ` Joseph Myers
2018-01-22 23:58 ` Rafal Luzynski [this message]
2018-01-23 20:23 ` Carlos O'Donell
2018-01-23 21:57 ` Rafal Luzynski
2018-01-17 22:38 ` Carlos O'Donell
2018-01-18 11:21 ` Florian Weimer
2018-01-18 11:59 ` Rafal Luzynski
2018-01-18 12:28 ` Florian Weimer
2018-01-18 13:31 ` Joseph Myers
2018-01-18 13:34 ` Florian Weimer
2018-01-12 4:19 ` Carlos O'Donell
2018-01-12 12:54 ` Adhemerval Zanella
2018-01-18 15:30 ` Dmitry V. Levin
2018-01-18 16:42 ` Adhemerval Zanella
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=1747850650.411713.1516665503888@poczta.nazwa.pl \
--to=digitalfreak@lingonborough.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@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).