From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Brandon Williams <bmwill@google.com>,
Stefan Beller <sbeller@google.com>
Subject: Re: What's cooking in git.git (May 2017, #01; Mon, 1)
Date: Mon, 1 May 2017 16:25:14 +0200 [thread overview]
Message-ID: <CACBZZX4ty91vh=ykMtpF0pV8Ru3BKWBXyQYsFRdPkKkxMd8pzw@mail.gmail.com> (raw)
In-Reply-To: <xmqqefw9gmvq.fsf@gitster.mtv.corp.google.com>
On Mon, May 1, 2017 at 7:35 AM, Junio C Hamano <gitster@pobox.com> wrote:
> * ab/clone-no-tags (2017-05-01) 3 commits
> (merged to 'next' on 2017-04-30 at 601649896a)
> + tests: rename a test having to do with shallow submodules
> + clone: add a --no-tags option to clone without tags
> + tests: change "cd ... && git fetch" to "cd &&\n\tgit fetch"
>
> "git clone" learned the "--no-tags" option not to fetch all tags
> initially, and also set up the tagopt not to follow any tags in
> subsequent fetches.
>
> Will cook in 'next'.
Thanks for trimming off the top 2 patches. I've dropped those myself,
if someone (Brandon || Stefan) more interested in working on
submodules wants to pick them up that would be neat, but I don't need
it myself & doing it differently than the existing submodule options
would take too much of my time.
> * ab/grep-pcre-v2 (2017-04-25) 20 commits
> - SQUASH???
> - Makefile & configure: make PCRE v2 the default PCRE implementation
> - grep: remove support for concurrent use of both PCRE v1 & v2
> - grep: add support for PCRE v2
> - grep: add support for the PCRE v1 JIT API
> - perf: add a performance comparison test of grep -E and -P
> - grep: change the internal PCRE code & header names to be PCRE1
> - grep: change the internal PCRE macro names to be PCRE1
> - test-lib: rename the LIBPCRE prerequisite to PCRE
> - grep: make grep.patternType=[pcre|pcre1] a synonym for "perl"
> - grep & rev-list doc: stop promising libpcre for --perl-regexp
> - log: add -P as a synonym for --perl-regexp
> - log: add exhaustive tests for pattern style options & config
> - grep: add a test for backreferences in PCRE patterns
> - Makefile & configure: reword outdated comment about PCRE
> - grep: remove redundant `regflags &= ~REG_EXTENDED` assignments
> - grep: remove redundant regflags assignment under PCRE
> - grep: submodule-related case statements should die if new fields are added
> - grep: add tests for grep pattern types being passed to submodules
> - grep: amend submodule recursion test in preparation for rx engine testing
>
> PCRE2, which has an API different from and incompatible with PCRE,
> can now be chosen to support "grep -P -e '<pattern>'" and friends.
That squash looks good to me.
> * ab/grep-threading-cleanup (2017-04-16) 8 commits
> - grep: given --threads with NO_PTHREADS=YesPlease, warn
> - pack-objects: fix buggy warning about threads under NO_PTHREADS=YesPlease
> - pack-object & index-pack: add test for --threads warning under NO_PTHREADS
> - tests: add a PTHREADS prerequisite
> - grep: skip pthreads overhead when using one thread
> - grep: don't redundantly compile throwaway patterns under threading
> - grep: add tests for --threads=N and grep.threads
> - grep: assert that threading is enabled when calling grep_{lock,unlock}
>
> Code cleanup.
>
> Needs review.
Between these two series there's 27 patches, and I understand it's a
bit of a PITA to review/get comments on it.
Anything I should be doing differently here other than just waiting
for 2.13 to come out so they can be cooked further & merged down to
next & then master if there's no objections?
next prev parent reply other threads:[~2017-05-01 14:25 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 5:35 What's cooking in git.git (May 2017, #01; Mon, 1) Junio C Hamano
2017-05-01 14:25 ` Ævar Arnfjörð Bjarmason [this message]
2017-05-01 16:21 ` Brandon Williams
2017-05-01 17:44 ` Ævar Arnfjörð Bjarmason
2017-05-01 19:29 ` Jeff King
2017-05-01 23:21 ` Junio C Hamano
2017-05-02 8:23 ` Ævar Arnfjörð Bjarmason
2017-05-02 9:35 ` Junio C Hamano
2017-05-02 12:31 ` Ævar Arnfjörð Bjarmason
2017-05-02 11:11 ` Johannes Schindelin
2017-05-02 12:09 ` PCRE v2 compile error, was " Johannes Schindelin
2017-05-02 12:27 ` Ævar Arnfjörð Bjarmason
2017-05-02 16:05 ` Johannes Schindelin
2017-05-02 18:52 ` Ævar Arnfjörð Bjarmason
2017-05-02 20:51 ` Kevin Daudt
2017-05-02 21:16 ` Ævar Arnfjörð Bjarmason
2017-05-03 9:45 ` Johannes Schindelin
2017-05-03 11:15 ` Duy Nguyen
2017-05-03 15:10 ` Ævar Arnfjörð Bjarmason
2017-05-04 9:11 ` Johannes Schindelin
2017-05-04 10:24 ` Ævar Arnfjörð Bjarmason
2017-05-04 11:32 ` Johannes Schindelin
2017-05-04 11:53 ` Ævar Arnfjörð Bjarmason
2017-05-08 6:30 ` Ævar Arnfjörð Bjarmason
2017-05-08 7:10 ` Junio C Hamano
2017-05-08 23:32 ` brian m. carlson
2017-05-09 0:00 ` Ævar Arnfjörð Bjarmason
2017-05-09 0:37 ` brian m. carlson
2017-05-09 10:40 ` Johannes Schindelin
2017-05-09 11:29 ` Ævar Arnfjörð Bjarmason
2017-05-09 11:12 ` Ævar Arnfjörð Bjarmason
2017-05-09 14:22 ` demerphq
2017-05-09 14:46 ` Ævar Arnfjörð Bjarmason
2017-05-02 17:43 ` Brandon Williams
2017-05-02 17:49 ` Ævar Arnfjörð Bjarmason
2017-05-05 1:12 ` Ramsay Jones
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='CACBZZX4ty91vh=ykMtpF0pV8Ru3BKWBXyQYsFRdPkKkxMd8pzw@mail.gmail.com' \
--to=avarab@gmail.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.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://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).