From: Junio C Hamano <gitster@pobox.com>
To: "Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Brandon Casey <drafnel@gmail.com>,
Philippe Blain <levraiphilippeblain@gmail.com>
Subject: Re: [PATCH 0/2] Improve and test Fortran xfuncname regex
Date: Thu, 13 Aug 2020 11:22:09 -0700 [thread overview]
Message-ID: <xmqqeeoa2ypa.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <pull.700.git.1597271429.gitgitgadget@gmail.com> (Philippe Blain via GitGitGadget's message of "Wed, 12 Aug 2020 22:30:27 +0000")
"Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com> writes:
> This series adds tests for the Fortran xfuncname regex and fixes a
> shortcoming of the regex.
Will queue. Thanks.
>
> Philippe Blain (2):
> userdiff: add tests for Fortran xfuncname regex
> userdiff: improve Fortran xfuncname regex
>
> t/t4018/fortran-block-data | 5 +++++
> t/t4018/fortran-comment | 13 +++++++++++++
> t/t4018/fortran-comment-keyword | 14 ++++++++++++++
> t/t4018/fortran-comment-legacy | 13 +++++++++++++
> t/t4018/fortran-comment-legacy-star | 13 +++++++++++++
> t/t4018/fortran-external-function | 9 +++++++++
> t/t4018/fortran-external-subroutine | 5 +++++
> t/t4018/fortran-module | 5 +++++
> t/t4018/fortran-module-procedure | 13 +++++++++++++
> t/t4018/fortran-program | 5 +++++
> userdiff.c | 6 +++++-
> 11 files changed, 100 insertions(+), 1 deletion(-)
> create mode 100644 t/t4018/fortran-block-data
> create mode 100644 t/t4018/fortran-comment
> create mode 100644 t/t4018/fortran-comment-keyword
> create mode 100644 t/t4018/fortran-comment-legacy
> create mode 100644 t/t4018/fortran-comment-legacy-star
> create mode 100644 t/t4018/fortran-external-function
> create mode 100644 t/t4018/fortran-external-subroutine
> create mode 100644 t/t4018/fortran-module
> create mode 100644 t/t4018/fortran-module-procedure
> create mode 100644 t/t4018/fortran-program
>
>
> base-commit: 4f0a8be78499454eac3985b6e7e144b8376ab0a5
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-700%2Fphil-blain%2Ffortran-better-userdiff-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-700/phil-blain/fortran-better-userdiff-v1
> Pull-Request: https://github.com/gitgitgadget/git/pull/700
prev parent reply other threads:[~2020-08-13 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 22:30 [PATCH 0/2] Improve and test Fortran xfuncname regex Philippe Blain via GitGitGadget
2020-08-12 22:30 ` [PATCH 1/2] userdiff: add tests for " Philippe Blain via GitGitGadget
2020-08-12 22:30 ` [PATCH 2/2] userdiff: improve " Philippe Blain via GitGitGadget
2020-08-13 2:10 ` Elijah Newren
2020-08-13 12:45 ` Philippe Blain
2020-08-13 14:04 ` Elijah Newren
2020-08-13 18:22 ` Junio C Hamano [this message]
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=xmqqeeoa2ypa.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=levraiphilippeblain@gmail.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.
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).