mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Re: [PATCH] regex: fix newline matching with negated brackets
Date: Sat, 18 Mar 2017 11:39:35 -0400	[thread overview]
Message-ID: <20170318153935.GQ1693@brightrain.aerifal.cx> (raw)
In-Reply-To: <4CAE9FC3-77C9-473B-9A48-345C81A578A7@gmail.com>

On Sat, Mar 18, 2017 at 04:00:11PM +0100, Julien Ramseier wrote:
> Again with inline patch.
> I suspect my emails are not received by anyone when adding an attachment...

No, attached patch is fine and preferable. I saw the patch but I'm
waiting for nsz (who understands the regex code much better) to check
and make sure it looks ok.

Rich


  reply	other threads:[~2017-03-18 15:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17 13:33 Julien Ramseier
2017-03-18 15:00 ` Julien Ramseier
2017-03-18 15:39   ` Rich Felker [this message]
2017-03-19  3:30   ` Szabolcs Nagy
2017-03-21 16:25     ` 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=20170318153935.GQ1693@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).