From: Kevin Bortis <kevin@bortis.ch>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: musl 1.0.x branch
Date: Sat, 7 Jun 2014 08:23:36 +0200 [thread overview]
Message-ID: <CALONj1exjdOA=gY3EgwfbHGSh4qp06HhAEz+kksBkD502_qeSQ@mail.gmail.com> (raw)
In-Reply-To: <20140606193920.GF6051@example.net>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
Hi
I also don't use the 1.0.x version because the 1.1.x branch at the moment
get a lot of new handy stuff. I would like something like the kernel
release model. Simply tag the 1.1.x branch as an RC and retag it, if no
regressions/bugs are found within a week or so. I think the most annoying
bugs, like not compiling on an architecture are easily found within that
timeframe.
Regards
Kevin
Am Freitag, 6. Juni 2014 schrieb :
> On Fri, Jun 06, 2014 at 01:56:17PM -0400, Rich Felker wrote:
> > I'm about to prepare the 1.0.3 release, and I've been thinking a bit
> > about the future of the 1.0.x branch. Specifically I'd like to gauge
> > the extent to which it's being used. So far cherry-picking fixes to it
>
> For us (the "Dapty" software repository at Aetey) there is no such thing
> as a "system-wide-version of the c library", neither any corresponding
> upgrade barrier whatsoever.
>
> From this point of view, given the ABI stability a single supported
> branch (in such a case "trunk") is fully sufficient.
>
> Thanks for musl, it is a pleasure to build against it.
>
> Rune
>
>
[-- Attachment #2: Type: text/html, Size: 1417 bytes --]
next prev parent reply other threads:[~2014-06-07 6:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 17:56 Rich Felker
2014-06-06 19:39 ` u-igbb
2014-06-07 6:23 ` Kevin Bortis [this message]
2014-06-07 13:16 ` Anthony G. Basile
2014-06-07 18:26 ` Gustavo Zacarias
2014-06-09 9:23 ` Natanael Copa
2014-06-09 20:08 ` Rich Felker
2014-06-10 9:43 ` u-igbb
2014-06-10 16:03 ` Rich Felker
2014-06-10 16:50 ` Laurent Bercot
2014-06-10 17:37 ` Rich Felker
2014-06-10 19:19 ` Laurent Bercot
2014-06-10 21:01 ` Rich Felker
2014-06-11 1:27 ` Laurent Bercot
2014-06-10 20:32 ` u-igbb
2014-06-10 21:51 ` Rich Felker
2014-06-11 10:24 ` u-igbb
2014-06-11 13:09 ` Rich Felker
2014-06-11 14:37 ` u-igbb
2014-06-10 21:25 ` Natanael Copa
2014-06-10 21:13 ` musl 1.0.x branch -- OT u-igbb
2014-06-10 21:55 ` musl 1.0.x branch Rich Felker
2014-06-11 10:41 ` Oliver Schneider
2014-06-11 13:16 ` Rich Felker
2014-06-12 18:46 ` Oliver Schneider
2014-06-13 1:23 ` Rich Felker
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='CALONj1exjdOA=gY3EgwfbHGSh4qp06HhAEz+kksBkD502_qeSQ@mail.gmail.com' \
--to=kevin@bortis.ch \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).