git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ed Maste <emaste@freebsd.org>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2019, #01; Mon, 2)
Date: Fri, 13 Dec 2019 11:02:44 -0800	[thread overview]
Message-ID: <xmqq1rt8kq0b.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAPyFy2BuWJJzC7F=H2KGgwANYdMNjisJ0ozK6VNqXui3=-=bBw@mail.gmail.com> (Ed Maste's message of "Fri, 13 Dec 2019 08:58:34 -0500")

Ed Maste <emaste@freebsd.org> writes:

> On Fri, 13 Dec 2019 at 08:38, Ed Maste <emaste@freebsd.org> wrote:
>>
>> On Mon, 2 Dec 2019 at 09:16, Junio C Hamano <gitster@pobox.com> wrote:
>> >
>> > * ln/userdiff-elixir (2019-11-10) 1 commit
>> >   (merged to 'next' on 2019-11-19 at 6318918ba8)
>> >  + userdiff: add Elixir to supported userdiff languages
>>
>> t4018-diff-funcname.sh is failing on FreeBSD with this change,
>> fatal: invalid regular expression:
>> |[@:]?[a-zA-Z0-9@_?!]+|[-+]?0[xob][0-9a-fA-F]+|[-+]?[0-9][0-9_.]*([eE][-+]?[0-9_]+)?|:?(\+\+|--|\.\.|~~~|<>|\^\^\^|<?\|>|<<<?|>?>>|<<?~|~>?>|<~>|<=|>=|===?|!==?|=~|&&&?|\|\|\|?|=>|<-|\\\\|->)|:?%[A-Za-z0-9_.]\{\}?|[^[:space:]]|[<C0>-<FF>][<80>-<BF>]+
>
> There was an empty subexpression in the first regex; just sent a patch
> to fix it.

Thanks.


  reply	other threads:[~2019-12-13 19:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 14:16 What's cooking in git.git (Dec 2019, #01; Mon, 2) Junio C Hamano
2019-12-02 15:59 ` Elijah Newren
2019-12-02 21:05 ` Denton Liu
2019-12-03 16:34   ` Junio C Hamano
2019-12-03 16:38   ` Junio C Hamano
2019-12-04  6:19     ` Denton Liu
2019-12-04 18:14       ` Junio C Hamano
2019-12-04 18:53 ` Derrick Stolee
2019-12-06 21:31   ` Junio C Hamano
2019-12-13 13:38 ` Ed Maste
2019-12-13 13:58   ` Ed Maste
2019-12-13 19:02     ` Junio C Hamano [this message]
2019-12-16  2:26 ` Heba Waly

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=xmqq1rt8kq0b.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=emaste@freebsd.org \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public 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).