This is why I labeled it as "if it were me". Of course I tend to 
take a harder view of whats the programmers responsibilities when releasing 
a package than most people. Maybe it has to do with my overbuilt sense of 
getting things done right and not being blamed for breaks too frequesntly. :)


On Fri, Dec 28, 2001 at 08:09:54AM -0700, Bdale Garbee wrote:
> [EMAIL PROTECTED] (Brian Wolfe) writes:
> 
> > Actualy, I believe that the mkisofs maintainer should have seen that a 
> > new option was created and notified the maintainers of anything that 
> > depended on mkisofs ...
> 
> That's pushing it, I think.  I've had several experiences as a maintainer
> where something in an upstream package changed that seemed insignificant to
> me, but which broke some other package that depended on mine.  These events
> aren't a big deal if everyone is "engaged" and bugs are getting addressed as
> they are reported.
> 
> Let's stick to the main problem.
> 
> Bdale
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 

-- 
--------------------------------------------------------------------------------
TerraBox.com    Fingerprint: 2849 5090 D4E0 2A6C C648  A750 52F8 8504 67DB 205C


Reply via email to