Hi Julian.
On 11.04.2013 05:10, Julian Foad wrote:
> Hi Matthias. Thanks for your email, and sorry it was so long before I looked
> back in my mailbox and replied.
>
> Matthias Buecher wrote on 2013-02-02:
>
>> the contrib script "detect-merge-conflicts.sh" [1] uses a grep command
>> which al
Hi Matthias. Thanks for your email, and sorry it was so long before I looked
back in my mailbox and replied.
Matthias Buecher wrote on 2013-02-02:
> the contrib script "detect-merge-conflicts.sh" [1] uses a grep command
> which also finds false positive merge conflict markers: it finds single
Alan, thanks for the info.
I have re-tested on NetBSD 5.0, Debian 6.0, Redhat on Sourceforge, FreeBSD 9
and also on OpenWrt/Busybox 1.19.4.
All sed versions support semicolon.
NetBSD needs newlines after closing brackets.
Busybox needs nested brackets for "p" and "q" to work correctly (also makes
On Wed, 20 Feb 2013, Matthias Buecher / Germany wrote:
I tested on Debian 6.0 Squeeze and on Sourceforge Redhat server.
Just installed FreeBSD 9.0 in a VM and sed on FreeBSD needs a
semicolon to separate last command and closing bracket.
Semicolon might often work, but the portable syntax requ
x27; output can be
> large).
>
> Gavin Baumanis wrote on Wed, Feb 20, 2013 at 09:10:48 -0500:
>> Ping.
>> This Patch submission has received no comments.
>>
>>
>>
>> > -Original Message-
>> > From: Matthias Buecher / Ge
On Wed, 20 Feb 2013, Daniel Shahaf wrote:
They seem to be invalid on BSD sed:
% printf 'foo\nbar\nbaz\n' | sed -ne '/foo/,/baz/ { /bar/p }'
sed: 1: "/foo/,/baz/ { /bar/p }
": extra characters at the end of p command
The close brace must be on a new line. This works on NetBSD:
$ printf 'foo\nb
t; > -Original Message-
> > From: Matthias Buecher / Germany [mailto:m...@maddes.net]
> > Sent: Saturday, 2 February 2013 15:20
> > To: dev@subversion.apache.org
> > Subject: [bug] detect-merge-conflicts.sh reports false positive merge
> > conflict
> > ma
Ping.
This Patch submission has received no comments.
> -Original Message-
> From: Matthias Buecher / Germany [mailto:m...@maddes.net]
> Sent: Saturday, 2 February 2013 15:20
> To: dev@subversion.apache.org
> Subject: [bug] detect-merge-conflicts.sh reports false
Hello,
the contrib script "detect-merge-conflicts.sh" [1] uses a grep command which
also finds false positive merge conflict markers: it finds single lines of
"===" and the pre-commit will fail.
For example I wanted to add a readme file that contains the following two lines:
Install
===
9 matches
Mail list logo
