[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-grep] Plan for grep

From: Aharon Robbins
Subject: Re: [bug-grep] Plan for grep
Date: Tue, 08 Mar 2005 22:04:34 +0200


> Date: Tue, 08 Mar 2005 09:07:41 +0100
> From: Stepan Kasal <address@hidden>
> Subject: [bug-grep] Plan for grep
> [ ... ]
> 2.5.2
> =====

> [ ... ]
> 4) check in the patches for the sync of dfa.c with GNU awk

Here, here!  :-)

Seriously though, this is a good thing to have. You may even
wish to put a ROADMAP file or some such into the dist and check
it into CVS.

> 2.5.3
> =====
> [ ... ]
> 2.6.x
> =====
> [ ... ]

It sounds like there are changes in store for dfa.[ch] above and beyond
what's in gawk.

Thus, I have a request, which is that if you have a "TODO" before
releasing, you add to it to drop dfa.[ch] into a copy of gawk and run
`make check'.

This need not be done very often, I probably would not sync any more
frequently than with each official release.  But if you (or "someone" :-)
can run a check of dfa.[ch] against gawk before releasing, it'll avoid
the hassle of my having to report a problem right after a release,
which is always disheartening.

(And if I'm in the middle of a test cycle, Stepan, please use whatever
tarball I've most recently released to my testers.)

> OK, we have plan.  I'm afraid I should invest my time to these points
> rather then to trying to be a good netizen and answer mails.

Yes, this is a hard thing to balance.  Maybe alternate days: one day
code, one day mail, one day code, one day mail....

And again, I am *so* glad that dfa.[ch] now have a home and a caretaker.

Much thanks,


reply via email to

[Prev in Thread] Current Thread [Next in Thread]