From: Rich Felker <email@example.com> To: James B <firstname.lastname@example.org> Cc: email@example.com, Johannes Schindelin <Johannes.Schindelin@gmx.de>, Jeff King <firstname.lastname@example.org>, email@example.com Subject: Re: [musl] Re: Regression: git no longer works with musl libc's regex impl Date: Tue, 4 Oct 2016 18:33:22 -0400 [thread overview] Message-ID: <20161004223322.GE19318@brightrain.aerifal.cx> (raw) In-Reply-To: <firstname.lastname@example.org> On Wed, Oct 05, 2016 at 09:06:25AM +1100, James B wrote: > On Tue, 4 Oct 2016 18:08:33 +0200 (CEST) > Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote: > > > > > No, it is not. You quote POSIX, but the matter of the fact is that we use > > a subset of POSIX in order to be able to keep things running on Windows. > > > > And quite honestly, there are lots of reasons to keep things running on > > Windows, and even to favor Windows support over musl support. Over four > > million reasons: the Git for Windows users. > > > > Wow, I don't know that Windows is a git's first-tier platform now, > and Linux/POSIX second. Are we talking about the same git that was > originally written in Linus Torvalds, and is used to manage Linux > kernel? Are you by any chance employed by Redmond, directly or > indirectly? > > Sorry - can't help it. I don't think the hostility and sarcasm are really needed here. But what this does speak to is that users don't like feeling like their platform is being treated as a second-class target, which is what it feels like when you have to manually flip a switch to make git build. This is especially unfriendly when the semantics of the switch come across, at least to some users, as "your system regex is incomplete" rather than "git can't use it because git depends on nonstandard extensions". Rich
next prev parent reply other threads:[~2016-10-04 22:33 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-10-04 15:08 Rich Felker 2016-10-04 15:27 ` Jeff King 2016-10-04 15:40 ` Rich Felker 2016-10-04 16:08 ` Johannes Schindelin 2016-10-04 16:11 ` Rich Felker 2016-10-04 17:16 ` Johannes Schindelin 2016-10-04 18:00 ` Ray Donnelly 2016-10-04 17:39 ` [musl] " Rich Felker 2016-10-05 11:17 ` Johannes Schindelin 2016-10-05 13:01 ` Szabolcs Nagy 2016-10-05 13:15 ` Rich Felker 2016-10-04 22:06 ` James B 2016-10-04 22:33 ` Rich Felker [this message] 2016-10-04 22:48 ` Junio C Hamano 2016-10-05 13:11 ` Jakub Narębski 2016-10-05 16:15 ` [musl] " Rich Felker 2016-10-05 10:41 ` Johannes Schindelin 2016-10-05 11:59 ` James B 2016-10-05 16:11 ` Jeff King 2016-10-05 16:27 ` Rich Felker 2016-10-06 10:44 ` Johannes Schindelin 2016-10-06 19:18 ` Ævar Arnfjörð Bjarmason 2016-10-06 19:23 ` Jeff King 2016-10-06 19:25 ` Rich Felker 2016-10-06 19:28 ` Jeff King 2016-10-06 22:42 ` Ramsay Jones 2016-10-07 11:30 ` Jakub Narębski 2016-10-04 16:01 ` Johannes Schindelin 2016-10-05 3:00 [musl] " writeonce 2016-10-05 10:49 ` Johannes Schindelin 2016-10-05 16:37 writeonce
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20161004223322.GE19318@brightrain.aerifal.cx \ --email@example.com \ --cc=Johannes.Schindelin@gmx.de \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [musl] Re: Regression: git no longer works with musl libc'\''s regex impl' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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).