[MPlayer-cvslog] CVS: main configure, 1.1044, 1.1045 Makefile, 1.329, 1.330
Rich Felker
dalias at aerifal.cx
Sun Aug 21 17:02:28 CEST 2005
On Sun, Aug 21, 2005 at 03:00:13PM +0300, Ivan Kalvachev wrote:
> Somehow I cannot imagine that You Michael will write an cvs explanation
> 6 times bigger than the patch itself ;)
> After all you are the master of 10^x,l cola explanations ;)
:))))))))))
> Severity is a litlle overkill
Not at all. Severity is the number of liters of cola! :)
> If there are sideeffects then the fix is bad.
Not necessarily. Suppose there's a compiletime error in some obscure
feature a newbie developer has just committed. I'm sure as hell going
to fix the compiletime error however I can, with a commit message like
"this feature may now be broken -- fix it properly or leave it alone".
This also happens when api changes in lavc break obscure features that
are using lavc, like the dvb stuff. Sometimes the person fixing the
module for the api change will not know the correct fix so they'll
just do enough to make sure it compiles.
> It is also not good idea to mark security-fix, as there are noobies
> that cann't find them without these tags :)
lol..
Rich
More information about the MPlayer-cvslog
mailing list