RE: Semantic errors

2019-03-25 Thread Randall S. Becker
> Of On March 25, 2019 15:22, Fabio Aiuto wrote: > Il giorno sab, 23/03/2019 alle 15.34 -0400, Randall S. Becker ha > scritto: > > On March 23, 2019 9:00, Fabio Aiuto wrote: > > > To: Randall S. Becker ; git@vger.kernel.org > > > Subject: Re: Semantic errors >

Re: Semantic errors

2019-03-25 Thread Fabio Aiuto
; > > To: Randall S. Becker ; git@vger.kernel > > > > .org > > > > Subject: Re: Semantic errors > > > > > > > > Il giorno ven, 22/03/2019 alle 18.43 -0400, Randall S. Becker > > > > ha > > > > scritto: > > > > >

Re: Semantic errors

2019-03-25 Thread Fabio Aiuto
Il giorno sab, 23/03/2019 alle 15.34 -0400, Randall S. Becker ha scritto: > On March 23, 2019 9:00, Fabio Aiuto wrote: > > To: Randall S. Becker ; git@vger.kernel.org > > Subject: Re: Semantic errors > > > > Il giorno ven, 22/03/2019 alle 18.43 -0400, Randa

RE: Semantic errors

2019-03-23 Thread Randall S. Becker
On March 23, 2019 9:00, Fabio Aiuto wrote: > To: Randall S. Becker ; git@vger.kernel.org > Subject: Re: Semantic errors > > Il giorno ven, 22/03/2019 alle 18.43 -0400, Randall S. Becker ha > scritto: > > > -Original Message- > > > From: Fabio Aiuto

Re: Semantic errors

2019-03-23 Thread Fabio Aiuto
Il giorno ven, 22/03/2019 alle 18.43 -0400, Randall S. Becker ha scritto: > > -Original Message- > > From: Fabio Aiuto > > Sent: March 22, 2019 17:41 > > To: Randall S. Becker ; git@vger.kernel.org > > Subject: Re: Semantic errors > > > >

Re: Semantic errors

2019-03-23 Thread Fabio Aiuto
Il giorno ven, 22/03/2019 alle 18.43 -0400, Randall S. Becker ha scritto: > > -Original Message- > > From: Fabio Aiuto > > Sent: March 22, 2019 17:41 > > To: Randall S. Becker ; git@vger.kernel.org > > Subject: Re: Semantic errors > > > >

RE: Semantic errors

2019-03-22 Thread Randall S. Becker
> -Original Message- > From: Fabio Aiuto > Sent: March 22, 2019 17:41 > To: Randall S. Becker ; git@vger.kernel.org > Subject: Re: Semantic errors > > Il giorno ven, 22/03/2019 alle 17.39 -0400, Randall S. Becker ha > scritto: > > On March 22, 2019 17:2

Re: Semantic errors

2019-03-22 Thread Fabio Aiuto
> > called > > > > > > "studio" based on master (last public commit e902e9b by > > > > > > Junio C > > > > > > Hamano on Monday March 11 2019). I've built everything by > > > > > > changing: >

RE: Semantic errors

2019-03-22 Thread Randall S. Becker
March 11 2019). I've built everything by > > > > > changing: > > > > > CFLAGS = -g -Wall (removing -O2 to have smooth trace in > > > > > debugging). > > > > > But the environment detects the following semantic errors (I > >

Re: Semantic errors

2019-03-22 Thread Fabio Aiuto
9b by Junio > > > > > C > > > > > Hamano on Monday March 11 2019). I've built everything by > > > > > changing: > > > > > CFLAGS = -g -Wall (removing -O2 to have smooth trace in > > > > > debugging). > > > &

Re: Semantic errors

2019-03-22 Thread Fabio Aiuto
t; changing: > > > > CFLAGS = -g -Wall (removing -O2 to have smooth trace in > > > > debugging). > > > > But the environment detects the following semantic errors (I > > > > made no > > > > edits!!!): > > > > Description

RE: Semantic errors

2019-03-22 Thread Randall S. Becker
> Of On March 22, 2019 16:25, Fabio Aiuto wrote: > To: Randall S. Becker ; git@vger.kernel.org > Subject: Re: Semantic errors > > Il giorno gio, 21/03/2019 alle 17.03 -0400, Randall S. Becker ha > scritto: > > > Of On March 21, 2019 15:32, Fabio Aiuto wrote: > >

Re: Semantic errors

2019-03-22 Thread Fabio Aiuto
t; changing: > > > > CFLAGS = -g -Wall (removing -O2 to have smooth trace in > > > > debugging). > > > > But the environment detects the following semantic errors (I > > > > made no > > > > edits!!!): > > > > Description

RE: Semantic errors

2019-03-21 Thread Randall S. Becker
quot;studio" based on master (last public commit e902e9b by Junio C > > > Hamano on Monday March 11 2019). I've built everything by changing: > > > CFLAGS = -g -Wall (removing -O2 to have smooth trace in debugging). > > > But the environment detects the f

Re: Semantic errors

2019-03-21 Thread Fabio Aiuto
unio C Hamano on Monday > > March 11 2019). I've built everything by changing: > > CFLAGS = -g -Wall (removing -O2 to have smooth trace in debugging). > > But the environment detects the following semantic errors (I made > > no > > edits!!!): > > Description Re

RE: Semantic errors

2019-03-21 Thread Randall S. Becker
= -g -Wall (removing -O2 to have smooth trace in debugging). > But the environment detects the following semantic errors (I made no > edits!!!): > Description ResourcePathLocationType > Symbol 'GIT_HTML_PATH' could not be resolved git.c /git >

Semantic errors

2019-03-21 Thread Fabio Aiuto
ing). But the environment detects the following semantic errors (I made no edits!!!): Description ResourcePathLocationType Symbol 'GIT_HTML_PATH' could not be resolvedgit.c /git line 154Semantic Error Symbol 'GIT_MAN_PATH' could

[PATCH v9 7/8] add a test for semantic errors in config files

2014-08-07 Thread Tanay Abhra
Semantic errors (for example, for alias.* variables NULL values are not allowed) in configuration files cause a die printing the line number and file name of the offending value. Add a test documenting that such errors cause a die printing the accurate line number and file name. Signed-off-by

[PATCH v8 7/8] add a test for semantic errors in config files

2014-08-06 Thread Tanay Abhra
Semantic errors (for example, for alias.* variables NULL values are not allowed) in configuration files cause a die printing the line number and file name of the offending value. Add a test documenting that such errors cause a die printing the accurate line number and file name. Signed-off-by

Re: [PATCH v7 7/8] add a test for semantic errors in config files

2014-08-04 Thread Junio C Hamano
Tanay Abhra writes: > + grep "fatal: bad config variable '\''alias.br'\'' at file line 2 in > .git/config" result This test is too tight (the full string), and also needs to know about i18n, I think. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message

[PATCH v7 7/8] add a test for semantic errors in config files

2014-08-01 Thread Tanay Abhra
Semantic errors (for example, for alias.* variables NULL values are not allowed) in configuration files cause a die printing the line number and file name of the offending value. Add a test documenting that such errors cause a die printing the accurate line number and file name. Signed-off-by

[PATCH v6 5/7] add a test for semantic errors in config files

2014-07-31 Thread Tanay Abhra
Semantic errors (for example, for alias.* variables NULL values are not allowed) in configuration files cause a die printing the line number and file name of the offending value. Add a test documenting that such errors cause a die printing the accurate line number and file name. Signed-off-by

[PATCH v5 5/7] add a test for semantic errors in config files

2014-07-31 Thread Tanay Abhra
Semantic errors (for example, for alias.* variables NULL values are not allowed) in configuration files cause a die printing the line number and file name of the offending value. Add a test documenting that such errors cause a die printing the accurate line number and file name. Signed-off-by

[PATCH v4 4/6] add a test for semantic errors in config files

2014-07-29 Thread Tanay Abhra
Semantic errors (for example, for alias.* variables NULL values are not allowed) in configuration files cause a die printing the line number and file name of the offending variable. Add a test documenting that such errors cause a die printing the the configuration variable, accurate line number

Re: [PATCH v3 4/6] add a test for semantic errors in config files

2014-07-28 Thread Matthieu Moy
Tanay Abhra writes: > On 7/28/2014 4:52 PM, Matthieu Moy wrote: >> Tanay Abhra writes: >> >>> +test_expect_success 'check line errors for malformed values' ' >>> + mv .git/config .git/config.old && >>> + test_when_finished "mv .git/config.old .git/config" && >>> + cat >.git/config <<-\EOF

Re: [PATCH v3 4/6] add a test for semantic errors in config files

2014-07-28 Thread Tanay Abhra
On 7/28/2014 4:52 PM, Matthieu Moy wrote: > Tanay Abhra writes: > >> +test_expect_success 'check line errors for malformed values' ' >> +mv .git/config .git/config.old && >> +test_when_finished "mv .git/config.old .git/config" && >> +cat >.git/config <<-\EOF && >> +[alias] >> +

Re: [PATCH v3 4/6] add a test for semantic errors in config files

2014-07-28 Thread Matthieu Moy
Tanay Abhra writes: > +test_expect_success 'check line errors for malformed values' ' > + mv .git/config .git/config.old && > + test_when_finished "mv .git/config.old .git/config" && > + cat >.git/config <<-\EOF && > + [alias] > + br > + EOF > + test_expect_cod

[PATCH v3 4/6] add a test for semantic errors in config files

2014-07-28 Thread Tanay Abhra
Semantic errors (for example, for alias.* variables NULL values are not allowed) in configuration files cause a die printing the line number and file name of the offending value. Add a test documenting that such errors cause a die printing the accurate line number and file name. Signed-off-by

[PATCH v2 4/6] add a test for semantic errors in config files

2014-07-25 Thread Tanay Abhra
Semantic errors (for example, for alias.* variables NULL values are not allowed) in configuration files cause a die printing the line number and file name of the offending value. Add a test documenting that such errors cause a die printing the accurate line number and file name. Signed-off-by

Re: [PATCH 3/7] add a test for semantic errors in config files

2014-07-24 Thread Junio C Hamano
Matthieu Moy writes: > Tanay Abhra writes: > > + test_when_finished "mv .git/config.old .git/config" && > + echo "[alias]\n br" >.git/config && >>> >>> Is the use of \n portable? >>> >> >> Yes, you are right, will replace with printf in the next patch. > > ... or a cat >.git/config <<\

Re: [PATCH 3/7] add a test for semantic errors in config files

2014-07-24 Thread Matthieu Moy
Tanay Abhra writes: + test_when_finished "mv .git/config.old .git/config" && + echo "[alias]\n br" >.git/config && >> >> Is the use of \n portable? >> > > Yes, you are right, will replace with printf in the next patch. ... or a cat >.git/config <<\EOF, since this is the construct u

Re: [PATCH 3/7] add a test for semantic errors in config files

2014-07-24 Thread Tanay Abhra
On 7/24/2014 3:41 AM, Junio C Hamano wrote: > Matthieu Moy writes: > >> Tanay Abhra writes: >> >>> +test_expect_success 'check line errors for malformed values' ' >>> + cp .git/config .git/config.old && > > Should this be "mv" not "cp"? You will be overwriting the file from > scratch in th

Re: [PATCH 3/7] add a test for semantic errors in config files

2014-07-23 Thread Junio C Hamano
Matthieu Moy writes: > Tanay Abhra writes: > >> +test_expect_success 'check line errors for malformed values' ' >> +cp .git/config .git/config.old && Should this be "mv" not "cp"? You will be overwriting the file from scratch in the later part of this test. >> +test_when_finished "mv

Re: [PATCH 3/7] add a test for semantic errors in config files

2014-07-23 Thread Matthieu Moy
Tanay Abhra writes: > +test_expect_success 'check line errors for malformed values' ' > + cp .git/config .git/config.old && > + test_when_finished "mv .git/config.old .git/config" && > + echo "[alias]\n br" >.git/config && > + test_expect_code 128 git br 2>result && > + grep "

[PATCH 3/7] add a test for semantic errors in config files

2014-07-23 Thread Tanay Abhra
Semantic errors (for example, for alias.* variables NULL values are not allowed) in configuration files cause a die printing the line number and file name of the offending value. Add a test documenting that such errors cause a die printing the accurate line number and file name. Signed-off-by