From owner-cvs-all Wed Aug 14 12:46:10 2002 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71BED37B400 for ; Wed, 14 Aug 2002 12:46:07 -0700 (PDT) Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B5C943E4A for ; Wed, 14 Aug 2002 12:46:06 -0700 (PDT) (envelope-from Jan.Stocker@t-online.de) Received: from fwd10.sul.t-online.de by mailout10.sul.t-online.com with smtp id 17f45C-0000Ak-04; Wed, 14 Aug 2002 21:45:30 +0200 Received: from twoflower.liebende.de (320072111332-0001@[217.80.127.40]) by fwd10.sul.t-online.com with esmtp id 17f455-1g0KsSC; Wed, 14 Aug 2002 21:45:23 +0200 Subject: Re: cvs commit: ports/games Makefile ports/games/lbreakout2 Makefile distinfo pkg-comment pkg-descr pkg-install pkg-plist From: Jan.Stocker@t-online.de (Jan Stocker) Reply-To: Jan.Stocker@t-online.de To: Mark Pulford Cc: Alexey Dokuchaev , Joseph Scott , cvs-all@freebsd.org In-Reply-To: <20020814224120.A24959@hamster.kyne.com.au> References: <1029314847.361.0.camel@twoflower> <20020814170155.A20454@regency.nsu.ru> <20020814224120.A24959@hamster.kyne.com.au> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 14 Aug 2002 21:45:33 +0200 Message-Id: <1029354334.365.11.camel@twoflower> Mime-Version: 1.0 X-Sender: 320072111332-0001@t-dialin.net Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG So what to do? Always send as what? And what to do after something like this happens.... a) We need to find a solution. So if you guys ignore the severity/priority what is your strategy? I think it should be oldest first, newest last and so this cant also happen. But what you did is maybe old to new in a special severity/priority but if you wanna ignore it, you must put you focus on a global sight. b) In the meantime the port owner has to be the first one, cause the existence of a second PR with the same port stuff shows that the second submitter hasnt understand that he has FIRST to search for a similar PR. And isn't fair to let the second one be maintainer. Something in my mind is a little bit angry and puts me in a distance, why doing a little bit work if you get ass-kicked? Okay.... it isnt so hard, but this isnt a quite good image you guys will have.... On Wed, 2002-08-14 at 15:11, Mark Pulford wrote: > Hi, > > What Alexey describes is pretty much what happened. The > severity/priority fields are mostly useless for determining anything > so I tend to ignore them. It just happens this time I was looking > through the non-critical section. > > Sorry for missing your port Jan. > > Regards, > Mark > > On Wed, Aug 14, 2002 at 05:01:55PM +0700, Alexey Dokuchaev wrote: > > I had *exactly* the same problem once. Committer said he was looking > > through non-critical section of PRs, while I noted my PR `serious'. > > Thus, he noticed my PR (submitted long, long before the latter) only > > afterwards. > > > > I think the problem is that "severity level" for ports PR is useless > > and causes more confusion than any good. Something gotta be done about > > this. Otherwise, ports "steals" will very likely happen again and > > again. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message