Date: Wed, 16 Apr 1997 14:39:41 +0200 From: "Julian H. Stacey" <jhs@freebsd.org> To: Scott Overholser <scotto@remuda.com> Cc: Zahemszky Gabor <zgabor@CoDe.hu>, freebsd-bugs@freebsd.org, hylafax@freebsd.org Subject: Re: HylaFAX broken on 2.2.0-R? Message-ID: <199704161239.OAA13028@wall.jhs.no_domain> In-Reply-To: Your message of "Tue, 15 Apr 1997 19:44:29 PDT." <Pine.NEB.3.93.970415191214.196A-100000@popeye.remuda.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Reference: > From: Scott Overholser <scotto@remuda.com> > > if this truely be a bug, what should happen next? as i mention below, > i've worked around the problem. i suppose someone should take steps to > make it right. i'll gladly file a bug if someone will clue me in on the > correct procedure. > > thanks, > -scotto man send-pr will tell you how to file bug reports for freebsd. (this is mainly used for src/ bugs ) But, ... please don't use it for hylafax :-) If you want to discuss freebsd specific bug symptoms, this is the list, if it'a a hylafax generic bug & patch discussion, see flexfax@sgi.com (I recall). you'll find their email & web address in the sources. If you write us a ports/comms/hylafax/patches/patch-* to recompile & test with .. great, folk (me inc.) on this list can review it, & maybe commit it, Other than that I (MAINTAINER as per hylafax/Makefile) am overloaded, & when I can find free time, i'm going to upgrade the release, unfortunately as a freelance who needs to find some paid work, I have to spend time finding that work, & have no extra time to debug other people's problems (I have enough of my own :-) Of course if anyone's looking to _pay_ me to debug their problems, that'd raise the priority about 10,000 per cent :-)) Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704161239.OAA13028>