public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* Re: Closing PRs for 3.4.1
       [not found]       ` <m3n03hia67.fsf@uniton.integrable-solutions.net>
@ 2004-06-07 13:08         ` Giovanni Bajo
  2004-06-07 17:10           ` Gabriel Dos Reis
  0 siblings, 1 reply; 2+ messages in thread
From: Giovanni Bajo @ 2004-06-07 13:08 UTC (permalink / raw)
  To: Gabriel Dos Reis; +Cc: gcc-patches, Gerald Pfeifer

Gabriel Dos Reis wrote:

>>> There is an agreement between Mark and I that he can retarget a
>>> regression present on gcc-3_3-branch and gcc-3_4-branch to the next
>>> release of 3.4.x, provided that he put me in the CC: and there is a
>>> notice to that effect.  It would be helpful if you (bugmasters)
>>> apply that strategy too.
>> 
>> Thank you for clarifying this. I'll try to remember to post a patch
>> for the website documentation about this policy.

Done thus. OK to commit?

Giovanni Bajo


Index: bugs/management.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/management.html,v
retrieving revision 1.23
diff -c -3 -p -r1.23 management.html
*** bugs/management.html        24 Jan 2004 10:13:57 -0000      1.23
--- bugs/management.html        7 Jun 2004 11:07:00 -0000
*************** marked as such.  The summary line should
*** 205,212 ****
  severity "<strong>critical</strong>" to bring it to attention. It may
  be downgraded later if a defect is not important enough to justify
  "critical" severity. In addition the target milestone should be set
! to the next release that needs fixing. The milestone can be changed
! by the release manager and his/her delegates.</p>

  <p><strong>If a patch fixing a PR has been submitted</strong>, a link
  to the message with the patch should be added to the PR, as well as the
--- 205,214 ----
  severity "<strong>critical</strong>" to bring it to attention. It may
  be downgraded later if a defect is not important enough to justify
  "critical" severity. In addition the target milestone should be set
! to the next release of the newest active release branch that needs
! fixing (the rationale is that a patch will have to go to the newest
! release branch before any other release branch). The milestone can
! be changed by the release manager and his/her delegates.</p>

  <p><strong>If a patch fixing a PR has been submitted</strong>, a link
  to the message with the patch should be added to the PR, as well as the


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Closing PRs for 3.4.1
  2004-06-07 13:08         ` Closing PRs for 3.4.1 Giovanni Bajo
@ 2004-06-07 17:10           ` Gabriel Dos Reis
  0 siblings, 0 replies; 2+ messages in thread
From: Gabriel Dos Reis @ 2004-06-07 17:10 UTC (permalink / raw)
  To: Giovanni Bajo; +Cc: Gabriel Dos Reis, gcc-patches, Gerald Pfeifer

You Wrote Giovanni Bajo
> Gabriel Dos Reis wrote:
>
>>>> There is an agreement between Mark and I that he can retarget a
>>>> regression present on gcc-3_3-branch and gcc-3_4-branch to the next
>>>> release of 3.4.x, provided that he put me in the CC: and there is a
>>>> notice to that effect.  It would be helpful if you (bugmasters)
>>>> apply that strategy too.
>>>
>>> Thank you for clarifying this. I'll try to remember to post a patch
>>> for the website documentation about this policy.
>
> Done thus. OK to commit?

Yes.  Thanks.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-06-07 15:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <40C22C5B.8080400@codesourcery.com>
     [not found] ` <1bc201c44b6b$87f85800$444e2a97@bagio>
     [not found]   ` <m3aczhjrlf.fsf@uniton.integrable-solutions.net>
     [not found]     ` <1c9f01c44b7a$fb183ee0$444e2a97@bagio>
     [not found]       ` <m3n03hia67.fsf@uniton.integrable-solutions.net>
2004-06-07 13:08         ` Closing PRs for 3.4.1 Giovanni Bajo
2004-06-07 17:10           ` Gabriel Dos Reis

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).