Fortran patch committed during freeze

[Manuel López-Ibáñez]

There is a 'svn lock' command that will send a warning to whoever
tries to commit but it doesn't work with directories yet.
http://svnbook.red-bean.com/nightly/en/svn.advanced.locking.html

Of course, you could do find .

On 12/02/07, Brooks Moses <brooks.moses@codesourcery.com> wrote:
> Roger Sayle wrote:
> > On Sun, 11 Feb 2007, Mark Mitchell wrote:
> >> However, please be mindful of the release branch freeze state in future.
> >
> > One comment I would make though, is how difficult it is to discover
> > the 4.1 branch's current status.  Neither the main page's "Current release
> > status" at http://gcc.gnu.org/ nor the most recently linked to status
> > e-mail from that page explicitly mention the/a freeze.  When
> > reviewing/approving a recent regression patch I had to infer that since
> > there was mention of a release candidate but there hadn't been a full
> > release, we were most likely frozen.  The 4.0 branch, however, is clearly
> > marked as frozen.
>
> I'll further note that it would really be useful to cc the fortran email
> list on announcements of branch freezes and the like, given that many
> (probably most) of the Fortran maintainers and contributors don't
> monitor the patches and devel lists.  Usually someone happens to notice
> and forwards a copy of the announcement over, but I think that got
> overlooked this time, with predictable results.
>
> - Brooks (adding a cc to fortran@ on this message as well)
>
>