This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: Change rules for adding/changing test cases
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Richard dot Earnshaw at arm dot com
- Cc: Richard Henderson <rth at redhat dot com>, DJ Delorie <dj at redhat dot com>, dewar at gnat dot com, gcc at gcc dot gnu dot org
- Date: Thu, 21 Mar 2002 12:34:34 +0100
- Subject: Re: RFC: Change rules for adding/changing test cases
- References: <20020320160715.A5492@redhat.com> <200203211121.LAA22747@cam-mail2.cambridge.arm.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Thu, Mar 21, 2002 at 11:21:00AM +0000, Richard Earnshaw wrote:
> There is a model of development/configuration management that says that
> every change to a product should be matched to a change request/defect
> report/enhancement specification etc, etc. I'm not suggesting that we
> should go down that route with gcc, it's probably overkill for this sort
> of community development, but it does have the advantage that the
> discussions/patches in the mailing lists would be more closely linked with
> the eventual changes made to the compiler. At present there is no easy
> way to get from a patch back to the reasons for the change.
Finding patch authors mail in gcc-patches list from the period around commit
usually works best (at least for me).
GNAT PRs usually don't contain too many details, which are usually present
on gcc-patches only (and only commits are appended to PRs automatically,
unlike the thread start on gcc-patches with all the details).
Jakub