Re: suggestion for future changes to GDB website

[Joel Brobecker <brobecker at adacore dot com>]

> > That's an option. The nice thing about posting the patch here is that
> > you can add an explaination to the patch. Revision histories are
> > sometimes a bit obscure...
> 
> What would you want to put in an explanation that doesn't belong in a
> log entry?

Most of the time, the RH will contain everything necessary, so nothing
more will be added. I don't have any example offhand of when an
explanation need to complete the RH. Perhaps after making a change
on which you want to start a discussion.

I think both formats are going to work. Whichever people want, I'm ok,
as long as we see the changes being made, and that we get a chance of
reacting to them.

All the developers who answered were in favor of posting the changes
one way or the other. Let's agree on one of the following forms:

  1. Post patch to gdb-patches BEFORE checkin
     Not sure how to make things work: Approval needed? Etc.

  2. Post patch to gdb-patches AFTER checkin

  3. Have an automated system that sends the patch with RH to
     a mailing-list. Could be a dedicated mailing-list, or one
     of the GDB existing mailing lists.

I'm OK with either of the proposals.

-- 
Joel