There is one subtlety: The old test case 'perl pattern gets full line of
POD header' does not have its own new test case, but the feature is
tested nevertheless by placing the RIGHT tag at the end of the expected
hunk header in t4018/perl-skip-sub-in-pod.
Signed-off-by: Johannes Sixt
Most of the tests show C++ code, but there is also a union definition and
a GNU style function definition that are not recognized.
Signed-off-by: Johannes Sixt j...@kdbg.org
---
t/t4018/cpp-class-constructor | 5 +
t/t4018/cpp-class-constructor-mem-init | 6 ++
All test cases that need a file with specific text patterns have been
converted to utilize texts in the t4018/ directory. The remaining tests
in the test script deal only with the validity of the regular
expressions. These tests do not depend on the contents of files that
'git diff' is invoked on.
A later patch changes the built-in cpp pattern. These test cases
demonstrate aspects of the pattern that we do not want to change.
Signed-off-by: Johannes Sixt j...@kdbg.org
---
t/t4018/cpp-c++-function | 4
t/t4018/cpp-class-definition | 4
For the test case matches to end of line, extend the pattern by a few
wildcards so that the pattern captures the RIGHT token, which is needed
for verification, without mentioning it in the pattern.
Signed-off-by: Johannes Sixt j...@kdbg.org
---
t/t4018-diff-funcname.sh | 40
The hunk header pattern 'cpp' is intended for C and C++ source code, but
it is actually not particularly useful for the latter, and even misses
some use-cases for the former.
The parts of the pattern have the following flaws:
- The first part matches an identifier followed immediately by a colon
On 03/21/2014 06:09 PM, Junio C Hamano wrote:
Eric Sunshine sunsh...@sunshineco.com writes:
Sorry, you're right about message[0] case not being a crasher (though
the assert() still seems overkill).
Assert() often becomes no-op in production build. I think this may
be an indication that
Jeff King p...@peff.net writes:
Several test scripts manually unset GIT_CONFIG and other
GIT_* variables. These are generally taken care of for us by
test-lib.sh already.
Unsetting these is not only useless, but can be confusing to
a reader, who may wonder why some tests in a script unset
On 03/21/2014 07:32 PM, Junio C Hamano wrote:
Matthias Beyer m...@beyermatthias.de writes:
I know, I can fix this by fixing the clean task in my Makefile. But
maybe someone somewhere on this world doesn't know the git internals
as good as me (and, of course, my coworker). Is there _any
Jeff King p...@peff.net writes:
Some tests want to check or set config in another
repository. E.g., t1000 creates repositories and makes sure
that their core.bare and core.worktree settings are what we
expect. We can do this with:
GIT_CONFIG=$repo/.git/config git config ...
but it
On Fri, Mar 21, 2014 at 5:13 PM, Michael Haggerty mhag...@alum.mit.edu wrote:
On 03/21/2014 06:09 PM, Junio C Hamano wrote:
Eric Sunshine sunsh...@sunshineco.com writes:
Sorry, you're right about message[0] case not being a crasher (though
the assert() still seems overkill).
Assert() often
Junio C Hamano gits...@pobox.com writes:
Torsten Bögershausen tbo...@web.de writes:
On 03/20/2014 10:09 PM, Junio C Hamano wrote:
* ap/remote-hg-skip-null-bookmarks (2014-03-19) 1 commit
- remote-hg: do not fail on invalid bookmarks
Will merge to 'next'.
Hmm, am I the only one who has
Hi Torsten,
On 21.03.2014, at 21:47, Torsten Bögershausen tbo...@web.de wrote:
On 2014-03-21 12.36, Max Horn wrote:
All tests passed :-),
Excellent.
thanks from my side.
comments inline, some are debatable
Thanks for having a close look and for the constructive feedback!
Unfortunately, I
On 03/21/2014 10:33 PM, Eric Sunshine wrote:
On Fri, Mar 21, 2014 at 5:13 PM, Michael Haggerty mhag...@alum.mit.edu
wrote:
On 03/21/2014 06:09 PM, Junio C Hamano wrote:
Assert() often becomes no-op in production build. I think this may
be an indication that table-driven may not be as good
Johannes Sixt j...@kdbg.org writes:
Add an infrastructure that simplifies adding new tests of the hunk
header regular expressions.
To add new tests, a file with the syntax to test can be dropped in the
directory t4018. The README file explains how a test file must contain;
s/how/what/, or
Thanks; will replace jk/diff-funcname-cpp-regex with this series.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Max Horn m...@quendi.de writes:
Hi Torsten,
On 21.03.2014, at 21:47, Torsten Bögershausen tbo...@web.de wrote:
On 2014-03-21 12.36, Max Horn wrote:
All tests passed :-),
Excellent.
thanks from my side.
comments inline, some are debatable
Thanks for having a close look and for the
[Please reply on-list to review comments. Other people may learn from
the discussion or have comments of their own.]
On Fri, Mar 21, 2014 at 6:00 PM, George Papanikolaou
g3orge@gmail.com wrote:
On Fri, Mar 21, 2014 at 4:48 AM, Eric Sunshine sunsh...@sunshineco.com
wrote:
Did you verify
Hi all,
At Facebook we've found that fetch speed is a bottleneck for our Git
repos, so we've been looking to deploy bitmaps to speed up fetches.
We've been trying out git-next with the top two patches from
https://github.com/peff/git/commits/jk/bitmap-reuse-delta, but the
following is
101 - 119 of 119 matches
Mail list logo