[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: (update) X crashes with Millenium II - bugfix thread
- From: Jeff DeMaagd <jdemaa17 calvin edu>
- To: axp-list redhat com
- Subject: Re: (update) X crashes with Millenium II - bugfix thread
- Date: Sat, 31 Oct 1998 23:43:52 -0500 (EST)
On Fri, 30 Oct 1998, Kurt Garloff wrote:
> this happens far too often in the free software development (and even more
> often with commercial apps): Somebody finds a problem, reports it and after
> some checking, one knows where the problem is. Somebody fixes it in a
> certain way. He's not very familiar with the code he fixes so the fix is
> probably not 100% clean. That's why he doesn't send it to the authors. He's
> satisfied with the proggie working at his place.
> If we're lucky, he upgrades his soft pretty often and after a couple of
> upgrades he's really fed up with having to fix it every time. Maybe he will
> create a clean patch and sent it to the Maintainer or maybe he will send his
> unclean patches to somebody cleanig it and sending it to the maintainer.
That's a good point. I'm not much of a good hacker - I just program
little stuff for myself, not having time or knowledge to dig into huge
projects like the kernel, compilers or libs. I know that myself and others
fix programs in little ways just to make it work, but forget or don't
think to submit the problem for correction. With the D1X (descent
source code) project, linux support has been merged from ldescent, but I
had to do lots of stuff to make it compile somewhat on Alpha, but it bombs
because a file is compiled that uses assembly, ignoring the no-asm flag in
the compile configuration. At least ldescent is a better product, source
and doc wise. :)
I would really like to kick ldescent up to variable resolutions and alpha
asm, but again, little experience and time stop me.
Jeff DeMaagd
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[]