Jeff, unless I'm mistaken you've taken over maintainence of the debian
packaging of quakeforge and you have fairly current packaging in the
quakeforge-current tree in their cvs. I remember that when knghtbrd
decided to remove quakeforge packages from debian, it was because of
technical problems
On Mon, Dec 31, 2001 at 01:12:25AM -0500, Joey Hess wrote:
Jeff, unless I'm mistaken you've taken over maintainence of the debian
packaging of quakeforge and you have fairly current packaging in the
quakeforge-current tree in their cvs. I remember that when knghtbrd
decided to remove
Joey Hess wrote:
Jeff, unless I'm mistaken you've taken over maintainence of the debian
packaging of quakeforge and you have fairly current packaging in the
quakeforge-current tree in their cvs. I remember that when knghtbrd
decided to remove quakeforge packages from debian, it was because
On Mon, Dec 31, 2001 at 07:02:43AM -0500, Jeff Teunissen wrote:
Jeff, unless I'm mistaken you've taken over maintainence of the debian
packaging of quakeforge and you have fairly current packaging in the
quakeforge-current tree in their cvs. I remember that when knghtbrd
decided to remove
Joseph Carter wrote:
On Mon, Dec 31, 2001 at 07:02:43AM -0500, Jeff Teunissen wrote:
Jeff, unless I'm mistaken you've taken over maintainence of the
debian packaging of quakeforge and you have fairly current packaging
in the quakeforge-current tree in their cvs. I remember that when
On Mon, Dec 31, 2001 at 11:51:44AM -0500, Jeff Teunissen wrote:
The stuff outside I have done. Back in March or so I designed a nice,
complex, and complete system for handling gamedata. It would work as
long as an engine using it had fs_* Cvars and config files. Unless of
course you did
6 matches
Mail list logo
