public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bryce McKinlay <mckinlay@redhat.com>
To: tromey@redhat.com
Cc: Java Patch List <java-patches@gcc.gnu.org>,
	gcc@gcc.gnu.org, Mark Mitchell <mark@codesourcery.com>
Subject: Re:
Date: Wed, 29 Jun 2005 18:48:00 -0000	[thread overview]
Message-ID: <42C2ECA9.3050707@redhat.com> (raw)
In-Reply-To: <m3d5q5b0pw.fsf@localhost.localdomain>

Tom Tromey wrote:

>I'm checking this in on the trunk.  If I remember I'll put it on the
>4.0 branch once it reopens (there are a fair number of patches pending
>for it ... I hope it reopens soon).
>  
>

Mark,

The extended freeze of the 4.0 branch is making things difficult for 
libgcj because we have a large backlog of runtime patches which we are 
unable to apply at this time. The longer the freeze continues, the more 
difficult it becomes for us to keep track of what needs applying and 
increases the chances that something will be forgotten, resulting in 
problems and wasted time further down the line.

Could we get an exemption from the freeze rules for low-risk, runtime 
only libgcj fixes as determined by the libgcj maintainers? 
Alternatively, could we rethink our release policy to ensure that the 
duration of freezes is minimized in the future? I do think that a hard 
freeze in the days leading up to a release is useful and important, but 
keeping it in place for weeks just because a couple of bugs remain 
unfixed doesn't seem helpful.

Thanks

Bryce

       reply	other threads:[~2005-06-29 18:48 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3d5q5b0pw.fsf@localhost.localdomain>
2005-06-29 18:48 ` Bryce McKinlay [this message]
2005-06-29 20:40   ` Re: Mark Mitchell
2005-06-29 21:54     ` Re: Jeffrey A Law
2005-06-29 23:17       ` Re: Joe Buck
2005-06-29 23:45         ` Re: hpux regression vs 4.0.1 Jeffrey A Law
2005-06-29 21:57     ` Geoffrey Keating
2005-06-29 23:43       ` Re: Aalokrai Porwal
2024-01-05  9:57 Nani Rodrigue
2024-01-05 10:34 ` Jonathan Wakely
2024-01-05 10:58   ` Re: LIU Hao
  -- strict thread matches above, loose matches on Subject: below --
2023-11-18 21:22 Zebediah Beck
2023-11-18 23:52 ` David Edelsohn
2023-11-18 23:57   ` Re: Zebediah Beck
2023-01-13  5:41 Re: father.dominic
2022-05-22 21:20 Skrab Skrab
2022-05-22 22:12 ` David Edelsohn
2021-06-12 23:32 nayeemislam031702
2021-06-12 23:35 ` Aaron Gyes
2011-09-23 22:54 Re: Lawrence Gutsin
2011-06-29 15:42 Re: nicole8509
     [not found] <20080618135807.GA15427@bromo.msbb.uc.edu>
2008-06-18 18:02 ` Mike Stump
2008-01-10 16:29 Selina Ewing
2005-08-01 14:18 Chunjiang Li
2005-08-01 14:37 ` Daniel Berlin
2005-07-15 21:22 Re: ИнфоПространство
2004-12-11  3:30 Re: Лада Власовна
2004-11-29  5:11 Re: Елена Климентьевна
     [not found] <044DA5B8-0E8E-11D9-80A2-000A95D7CD40@apple.com>
     [not found] ` <9D4EDFF8-0E91-11D9-AC54-000393A91CAA@apple.com>
2004-09-25 10:54   ` Re: Dale Johannesen
2004-09-25 11:14     ` Re: Daniel Berlin
2004-09-25 11:31     ` Re: Richard Henderson
2004-09-07 13:59 Problem with operand handling Richard Kenner
2004-09-07 14:41 ` Diego Novillo
2004-09-07 14:51   ` Andrew MacLeod
2004-09-07 15:46     ` Nathan Sidwell
2004-09-07 15:55       ` Re: Andrew MacLeod
     [not found] <200305221636.h4MGaLDA010075@mururoa.inria.fr>
2003-05-22 16:45 ` Re: Daniel Berlin
2002-10-18 16:20 Re: Josep Maria
2002-10-18 16:22 ` Re: Josep Maria
2002-09-04 22:16 Re: ZMSECTT-2
2001-12-10 19:14 Re: Richard Kenner
1998-04-08  2:13 No Subject Yuan Xie
1998-04-08 15:08 ` Jeffrey A Law
1998-03-27 15:18 No Subject Ken Faiczak
1998-03-31  0:46 ` Jeffrey A Law
1998-02-10  3:34 Re: Jochen Kuepper
1998-02-10 10:30 ` Re: Jeffrey A Law
1998-02-09 14:46 No Subject Jochen Kuepper
1998-02-09 15:37 ` Jeffrey A Law
1997-12-05 13:11 No Subject Thomas Weise
1997-12-06  9:23 ` Jeffrey A Law
1997-08-26 21:22 (no subject) Eliot Dresselhaus
1997-10-17 23:35 ` Jeffrey A Law

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42C2ECA9.3050707@redhat.com \
    --to=mckinlay@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).