git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: What's cooking in git.git (Aug 2010, #04; Wed, 18)
Date: Thu, 19 Aug 2010 10:06:55 +0200	[thread overview]
Message-ID: <4C6CE61F.7060305@viscovery.net> (raw)
In-Reply-To: <20100819030237.GE18922@burratino>

Am 8/19/2010 5:02, schrieb Jonathan Nieder:
> Junio C Hamano wrote:
> 
>> * ab/compat-regex (2010-08-17) 5 commits
>>  - autoconf: don't use platform regex if it lacks REG_STARTEND
>>  - t/t7008-grep-binary.sh: un-TODO a test that needs REG_STARTEND
>>  - Change regerror() declaration from K&R style to ANSI C (C89)
>>  - compat/regex: get the gawk regex engine to compile within git
>>  - compat/regex: use the regex engine from gawk for compat
> 
> As Hannes noticed, the tip commit is bogus and the configure
> test gives the wrong result on platforms with missing or inferior
> regex.  Sorry about that.  Replacement is at $gmane/153782.

and I see these warnings:

In file included from compat/regex/regex.c:71:
compat/regex/regex_internal.c: In function 're_string_reconstruct':
compat/regex/regex_internal.c:696: warning: unused variable 'prev_valid_len'
In file included from compat/regex/regex.c:78:
compat/regex/regexec.c: In function 'check_arrival_add_next_nodes':
compat/regex/regexec.c:3062: warning: unused variable 'err'

This happens because RE_ENABLE_I18N is not defined by regex_internal.h. Is
this how it is supposed to be?

-- Hannes

  reply	other threads:[~2010-08-19  8:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 22:27 What's cooking in git.git (Aug 2010, #04; Wed, 18) Junio C Hamano
2010-08-19  3:02 ` Jonathan Nieder
2010-08-19  8:06   ` Johannes Sixt [this message]
2010-08-19 12:48     ` Ævar Arnfjörð Bjarmason
2010-08-19 15:04       ` Ævar Arnfjörð Bjarmason
     [not found]       ` <AANLkTinkjsLycvV-uvfG14t7Q=uKt+pnpizKCPGirVW1@mail.gmail.com>
2010-08-19 18:05         ` Fwd: " Aharon Robbins
2010-08-19 18:30           ` [PATCH] compat/regex: define out variables only used under RE_ENABLE_I18N Ævar Arnfjörð Bjarmason
2010-08-19 20:02             ` Junio C Hamano
2010-08-19 20:31               ` Ævar Arnfjörð Bjarmason
2010-08-19 21:07                 ` Junio C Hamano
2010-08-19 21:30                   ` Ævar Arnfjörð Bjarmason
2010-08-19 22:45                   ` [PATCH] compat/regex: get rid of old-style definition Junio C Hamano
2010-08-20  7:47                     ` Ævar Arnfjörð Bjarmason
2010-08-25 18:24                     ` Karsten Blees
2010-08-26  7:58                       ` [PATCH] Fix compat/regex ANSIfication on MinGW Johannes Sixt
2010-08-26 20:34                         ` Ævar Arnfjörð Bjarmason
2010-09-03 21:23                         ` karsten.blees
2010-09-03 22:21                           ` Ævar Arnfjörð Bjarmason
2010-09-04  5:22                             ` Junio C Hamano
2010-09-07 12:56                           ` Johannes Sixt
2010-08-19  3:22 ` jn/update-contrib-example-merge in pu Jonathan Nieder
2010-08-19 12:53 ` What's cooking in git.git (Aug 2010, #04; Wed, 18) Ævar Arnfjörð Bjarmason
2010-08-19 15:27   ` Ævar Arnfjörð Bjarmason

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=4C6CE61F.7060305@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@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).