RFC: Change rules for adding/changing test cases

[Jakub Jelinek]

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