public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@redhat.com>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Cc: pedro@palves.net, kevinb@redhat.com, brobecker@adacore.com,
	simon.marchi@polymtl.ca, tom@tromey.com, tdevries@suse.de,
	ulrich.weigand@de.ibm.com, eliz@gnu.org
Subject: Re: [PATCH v3 1/1] [gdb]: add git trailer information on gdb/MAINTAINERS
Date: Tue, 4 Jul 2023 17:08:47 +0200	[thread overview]
Message-ID: <78b12209-4837-bdd5-8ed0-6bab200b8555@redhat.com> (raw)
In-Reply-To: <878rbxm07o.fsf@redhat.com>

On 03/07/2023 18:25, Andrew Burgess wrote:
>> + - Tested-by:
>> +
>> +   Used when a contributor has tested the patch and finds that it
>> +   fixes the claimed problem.  It may also be used to indicate that
>> +   the contributor has performed regression testing.  By itself, this
>> +   tag says nothing about the quality of the fix implemented by the
>> +   patch.
> Given the number of different ways that tests can be run, and that you
> specifically say "It_may_  also be used to indicate ...", I wonder if
> it's worth extending the last sentence to specifically say:
>
>    By itself, this tag says nothing about the quality of the fix
>    implemented by the patch, nor the amount of testing that was actually
>    performed.
>
> Some people might give a (tb) tag just for running the tests added by
> the commit in question, while others might run the full testsuite on a
> unix board, while others might do a full regression test using multiple
> different boards.  The tag itself tells us very little really.
>
I'm not opposed to making this document somewhat prescriptive. If you 
think (and folks agree, of course) that as the tag is describe it tells 
us TOO little, we could instead require that people do some level of 
testing. My original idea would be that the person giving the tb tag 
would at least run a full run of the testsuite on the default board, but 
I changed it based on previous feedback. Or I can just add this change, 
whichever you prefer

-- 
Cheers,
Bruno


  reply	other threads:[~2023-07-04 15:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 12:42 [PATCH v3 0/1] update MAINTAINERS file with git trailers Bruno Larsen
2023-06-28 12:42 ` [PATCH v3 1/1] [gdb]: add git trailer information on gdb/MAINTAINERS Bruno Larsen
2023-06-30 21:07   ` Kevin Buettner
2023-07-03  8:36     ` Bruno Larsen
2023-07-03 16:25   ` Andrew Burgess
2023-07-04 15:08     ` Bruno Larsen [this message]
2023-07-06  1:46       ` Kevin Buettner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=78b12209-4837-bdd5-8ed0-6bab200b8555@redhat.com \
    --to=blarsen@redhat.com \
    --cc=aburgess@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=pedro@palves.net \
    --cc=simon.marchi@polymtl.ca \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.com \
    --cc=ulrich.weigand@de.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).