* Alexandre Duret-Lutz wrote on Wed, May 10, 2006 at 09:39:01PM CEST:
> >>> "RW" == Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> RW> OK?
>
> Yes please
Applied, thanks!
> RW> * tests/overrid.test: Change all regexes for warning messages to
> RW> match after a colon, so that the prepende
>>> "RW" == Ralf Wildenhues <[EMAIL PROTECTED]> writes:
RW> OK?
Yes please
RW> * tests/overrid.test: Change all regexes for warning messages to
RW> match after a colon, so that the prepended file names do not
RW> cause false matches. Tighten overrides regex. Fix typo
RW> `cleam-am-local
Hello,
On Thu, Apr 27, 2006 at 07:30:46AM +0200, Ralf Wildenhues wrote:
> > > fail because of `ps' in ``pwd`'.
I misunderstood this: I thought that a file named `ps' is in the
current dir, while you meant that `ps' is a substring the full
pathname of the current dir.
Having that mis-interpreatio
Hi Stepan,
* Stepan Kasal wrote on Thu, Apr 27, 2006 at 07:25:16AM CEST:
> On Wed, Apr 26, 2006 at 10:48:05PM +0200, Ralf Wildenhues wrote:
> > The failure I stumbled over was the `grep ps stderr' that didn't
> > fail because of `ps' in ``pwd`'.
>
> how could that happen? Do you mean that grep b
Hello Ralf,
On Wed, Apr 26, 2006 at 10:48:05PM +0200, Ralf Wildenhues wrote:
> The failure I stumbled over was the `grep ps stderr' that didn't
> fail because of `ps' in ``pwd`'.
how could that happen? Do you mean that grep behaved as
grep '' ps stderr?
Or did the string "ps" got to stderr some
OK? The failure I stumbled over was the `grep ps stderr' that didn't
fail because of `ps' in ``pwd`'.
Cheers,
Ralf
* tests/overrid.test: Change all regexes for warning messages to
match after a colon, so that the prepended file names do not
cause false matches. Tighten o
