From: "Michał Kiedrowicz" <michal.kiedrowicz@gmail.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2011, #08; Mon, 16)
Date: Tue, 17 May 2011 19:39:10 +0000 (UTC) [thread overview]
Message-ID: <loom.20110517T213130-515@post.gmane.org> (raw)
In-Reply-To: 7vwrhphllf.fsf@alter.siamese.dyndns.org
(Sending from gmane "followup" interface, don't blame me if CC list is not OK.)
Junio C Hamano <gitster <at> pobox.com> writes:
>
> * mk/grep-pcre (2011-05-16) 12 commits
> (merged to 'next' on 2011-05-16 at 0c6c25e)
> + Makefile: Pass USE_LIBPCRE down in GIT-BUILD-OPTIONS
> + git-grep: update tests now regexp type is "last one wins"
> (merged to 'next' on 2011-05-15 at d110135)
> + git-grep: do not die upon -F/-P when grep.extendedRegexp is set.
> + git-grep: Bail out when -P is used with -F or -E
> + grep: Add basic tests
> + configure: Check for libpcre
> + git-grep: Learn PCRE
> + grep: Extract compile_regexp_failed() from compile_regexp()
> + grep: Fix a typo in a comment
> (merged to 'next' on 2011-05-08 at 5d3bede)
> + grep: Put calls to fixmatch() and regmatch() into patmatch()
> + contrib/completion: --line-number to git grep
> + Documentation: Add --line-number to git-grep synopsis
>
> Fixed up the build procedure that did not update GIT-BUILD-OPTIONS.
> Will merge to "master" by the middle of week #5.
Thanks for your help with last few patches, Junio. Unfortunately, I didn't have
to time to work on testcases you wrote in comments to my last posting, but I'll
try to prepare some during this week.
prev parent reply other threads:[~2011-05-17 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 6:45 What's cooking in git.git (May 2011, #08; Mon, 16) Junio C Hamano
2011-05-17 19:39 ` Michał Kiedrowicz [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=loom.20110517T213130-515@post.gmane.org \
--to=michal.kiedrowicz@gmail.com \
--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.
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).