This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Revert "PowerPC shrink-wrap support 3 of 3"


On Thu, 10 Nov 2011, Hans-Peter Nilsson wrote:
> I think I need someone with appropriate write privileges to
> agree with that, and to also give 48h for someone to fix the
> problem.  Sorry for not forthcoming on the second point.
> 
> brgds, H-P
> PS. where is the policy written down, besides the mailing list archives?

https://gcc.gnu.org/develop.html has had the following since 2003 or so:

  Patch Reversion

  If a patch is committed which introduces a regression on any target 
  which the Steering Committee considers to be important and if:

   * the problem is reported to the original poster;
   * 48 hours pass without the original poster or any other party 
     indicating that a fix will be forthcoming in the very near future;
   * two people with write privileges to the affected area of the compiler 
     determine that the best course of action is to revert the patch;

  then they may revert the patch.

  (The list of important targets will be revised at the beginning of each 
  release cycle, if necessary, and is part of the release criteria.)

  After the patch has been reverted, the poster may appeal the decision to 
  the Steering Committee.

  Note that no distinction is made between patches which are themselves 
  buggy and patches that expose latent bugs elsewhere in the compiler.

This is there as part of the overall (release) methodology, though
svnwrite.html would be at least as natural.  Perhaps a reference
there?  Thoughts?

Gerald

PS: Yes, I am catching up with some older mails. ;-)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]