bug#54006: closed (Duplicate test)

[GNU bug Tracking System]

Your message dated Tue, 15 Feb 2022 09:41:57 -0800
with message-id 
<CA+8g5KHcJL+JQhSWq9LZjJR1B9c3LunimenO9h8E85uYfM17fw@mail.gmail.com>
and subject line Re: bug#54006: Duplicate test
has caused the debbugs.gnu.org bug report #54006,
regarding Duplicate test
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
54006: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=54006
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: Duplicate test Date: Tue, 15 Feb 2022 00:06:50 +0100

Greetings,

there's a duplicate test in tests/empty, see attached patch.

I'm working on a few other improvements, so please provide feedback if
there's anything I should do differently in the future.

Cheers!

Uli

gnu-grep-duplicate-test.patch
Description: Text Data

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#54006: Duplicate test
>
>
>
>
> Date: 
>
> Tue, 15 Feb 2022 09:41:57 -0800
>
>
>
>
> On Mon, Feb 14, 2022 at 8:42 PM Ulrich Eckhardt
> <ulrich.eckhardt@base-42.de> wrote:
> > there's a duplicate test in tests/empty, see attached patch.
> >
> > I'm working on a few other improvements, so please provide feedback if
> > there's anything I should do differently in the future.
>
> Thank you. I've applied that, edited the commit log to make it
> conform, and pushed.
> See the file HACKING for policy on how to write Emacs-style ChangeLog
> entries for grep commit logs. E.g., title is not a sentence and
> usually has no punctuation. And each affected file name is called out.
> Sometimes function names are also listed, e.g.,
>
> * dir/file_name (func1, func2): Description.
>
>
> --- End Message ---