[Python-Dev] forwarded message from noreply@sourceforge.net

Fred L. Drake, Jr. fdrake@beopen.com
Thu, 6 Jul 2000 17:41:43 -0400 (EDT)

Content-Type: text/plain; charset=us-ascii
Content-Description: message body and .signature
Content-Transfer-Encoding: 7bit

  Looks like the bug manager works much like we wish the patch manager


Fred L. Drake, Jr.  <fdrake at beopen.com>
BeOpen PythonLabs Team Member

Content-Type: message/rfc822
Content-Description: forwarded message
Content-Transfer-Encoding: 7bit

Return-Path: <nobody@sourceforge.net>
Received: from delerium.i.sourceforge.net (sourceforge.net [])
	by mailhost.beopen.com (8.9.3/8.9.3) with ESMTP id OAA20677
	for <fdrake@beopen.com>; Thu, 6 Jul 2000 14:33:37 -0700
Received: (from nobody@localhost)
	by delerium.i.sourceforge.net (8.9.3/8.9.3) id OAA04044;
	Thu, 6 Jul 2000 14:34:48 -0700
Message-Id: <200007062134.OAA04044@delerium.i.sourceforge.net>
From: noreply@sourceforge.net
To: fdrake@beopen.com, 0@delerium.i.sourceforge.net
Subject: [Bug #108997] CVS browsing should show old locks
Date: Thu, 6 Jul 2000 14:34:48 -0700

Bug #108997, was updated on 2000-Jul-06 17:21
Here is a current snapshot of the bug.

Project: SourceForge
Category: User Interface
Status: Open
Resolution: None
Bug Group: None
Priority: 5
Summary: CVS browsing should show old locks

Details: Browsing the CVS repository of a project should show locks files older than a couple of minutes.  This can help diagnose problems, such as (fairly common) read locks that weren't properly removed.


Date: 2000-Jul-06 17:34
By: montanaro

Agreed.  As someone who has somehow left two locks laying about in the Python repository (and caused a fair amount of needless grief in the process), I would like to have this information.  I suggest adding an extra column to the CVS browse listings.  It would be great if you gave a way for developers to remove their own stale locks (perhaps by highlighting those locks with a link as appropriate).

Skip Montanaro


For detailed info, follow this link: