Date: Tue, 20 Aug 2002 13:47:55 +0200 From: "Thomas E. Zander" <riggs@rrr.de> To: ports@freebsd.org Subject: Re: Why isn't ports/41614 going to be committed? Message-ID: <20020820114755.GE31501@f113.hadiko.de> In-Reply-To: <20020820125706.72f9623f.corecode@corecode.ath.cx> References: <20020820075906.GA31501@f113.hadiko.de> <20020820125706.72f9623f.corecode@corecode.ath.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 20. Aug 2002, at 12:57 +0200, Simon 'corecode' Schubert wrote according to [Re: Why isn't ports/41614 going to be committed?]: > patience is a virtue. ports committers have lots of things to do and are > doing stuff in their free time. patches also need to be tested (more or > less) extensively so that the resulting port builds and runs well. > if there is no ports committer working with linux-eagle himself, it's > hard to try out for him.... I just wanted to know if there is a specific problem that prohibits the update to be committed. I wouldn't ask if it was a compilcated story that breaks dependencies or something. So I hope that somebody will take a look at it when he's got enough time to do it. Thank you Riggs -- - "[...] I talked to the computer at great length and -- explained my view of the Universe to it" said Marvin. --- And what happened?" pressed Ford. ---- "It committed suicide." said Marvin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020820114755.GE31501>