xfs
[Top] [All Lists]

Re: pre releases in the CVS + Re: CLOSE 820228 - ASSERT trip in qa 017

To: GCS <gcs@xxxxxxxxxxxxxxxx>
Subject: Re: pre releases in the CVS + Re: CLOSE 820228 - ASSERT trip in qa 017
From: Eric Sandeen <sandeen@xxxxxxx>
Date: Wed, 11 Apr 2001 21:32:31 -0500
Cc: linux-xfs@xxxxxxxxxxx
References: <200104091535.IAA44417@xxxxxxxxxxxxxxxxx> <20010409174429.A9996@xxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
Hi Laszlo - 

We generally don't include pre-releases or other patches in the CVS tree
unless there's a _really_ pressing bug that's affecting development.  
Each merge takes time, and handling all of the prereleases would be a
lot of overhead.

Regarding the "bugworks" URL, you're correct - it's only accessible on
SGI's internal network.  It's not that there are any big secrets in
BugWorks for linux-xfs, it's just the way our infrastructure is set up. 
It would be great to use bugzilla, or some other tracking system that's
available on the internet, but we need to follow SGI's procedures for
tracking bugs, which means using BugWorks.

Perhaps we could write something that would copy linux-xfs bug reports
out to bugzilla - that would be an interesting project.  :)

-Eric

GCS wrote:
> 
> Hello,
> 
> Will SGI introduce the kernel pre releases into the CVS? I do not want to
> upgrade to 2.4.3 until the locking problems are fixed. And it seems SGI only
> bump the CVS up on major kernel releases.
> 
> On H, ÁPR 09, 2001 at 08:35:26 -0700, lord@xxxxxxx wrote:
> > View Incident: 
> > http://co-op.engr.sgi.com/BugWorks/code/bwxquery.cgi?search=Search&wlong=1&view_type=Bug&wi=820228
>  Am I wrong when I say it is not for public access? At lease I can not reach
> it. :-/
> 
> Thanks, Laszlo

<Prev in Thread] Current Thread [Next in Thread>