From livid-dev@livid.on.openprojects.net Mon, 13 Dec 1999 10:47:32 -0800 Date: Mon, 13 Dec 1999 10:47:32 -0800 From: livid cvs livid-dev@livid.on.openprojects.net Subject: [Livid-dev] cvs: mpav CVSROOT: /cvs/livid Module name: mpeg2dec Changes by: mpav 99/12/13 10:47:32 Log message: Aaron's mpeg2dec. Status: Vendor Tag: livid Release Tags: start N mpeg2dec/Makefile.in N mpeg2dec/README N mpeg2dec/stamp-h.in N mpeg2dec/Makefile.am N mpeg2dec/TODO N mpeg2dec/acconfig.h N mpeg2dec/aclocal.m4 N mpeg2dec/config.guess N mpeg2dec/config.h.in N mpeg2dec/config.sub N mpeg2dec/configure N mpeg2dec/configure.in N mpeg2dec/install-sh N mpeg2dec/missing N mpeg2dec/mkinstalldirs N mpeg2dec/display.c N mpeg2dec/getvlc.c N mpeg2dec/mb_buffer.c N mpeg2dec/motion.c N mpeg2dec/parse.c N mpeg2dec/stats.c N mpeg2dec/idct.c N mpeg2dec/motion_comp.c N mpeg2dec/inv_quantize.c N mpeg2dec/decode.c N mpeg2dec/bitstream.c N mpeg2dec/debug.c N mpeg2dec/config.h N mpeg2dec/getvlc.h N mpeg2dec/stats.h N mpeg2dec/parse.h N mpeg2dec/slice.h N mpeg2dec/mb_buffer.h N mpeg2dec/motion_comp.h N mpeg2dec/inv_quantize.h N mpeg2dec/mpeg2.h N mpeg2dec/mpeg2_internal.h N mpeg2dec/display.h N mpeg2dec/idct.h N mpeg2dec/old_config.h N mpeg2dec/global.h N mpeg2dec/old_crap.h N mpeg2dec/mpeg2dec.h N mpeg2dec/debug.h N mpeg2dec/bitstream.h N mpeg2dec/Changelog N mpeg2dec/display_mga_vid.c N mpeg2dec/display_x11.c N mpeg2dec/tools/Makefile.in N mpeg2dec/tools/Makefile.am N mpeg2dec/tools/extract_mpeg2.c N mpeg2dec/drivers/Makefile.in N mpeg2dec/drivers/README N mpeg2dec/drivers/Makefile.am N mpeg2dec/drivers/mga_vid.c N mpeg2dec/drivers/mga_vid_test.c N mpeg2dec/drivers/mga_vid.h No conflicts created by this import
From aholtzma@ess4.engr.UVic.CA Mon, 13 Dec 1999 17:43:54 -0800 Date: Mon, 13 Dec 1999 17:43:54 -0800 From: Aaron Holtzman aholtzma@ess4.engr.UVic.CA Subject: [Livid-dev] cvs: mpav Speaking of cvs, I have a proposal to make. I would like to move all new development to sourceforge in the near future. I honestly don't trust the openprojects setup after this summers ludicrous outage. The guys at sourceforge seem to have their act together. I also think we're going to need some kind of bugtracking soon. Every release I do, I get mailbombed with reports of this or that. mutt doesn't make a good bug database :) I often wonder how someone like Alan Cox can process _so_ much email and remember which patch goes where and who it came from. Anyways, any thoughts/flames? yea's or nea's? cheers, aaron
From alan@lxorguk.ukuu.org.uk Tue, 14 Dec 1999 01:53:37 +0000 (GMT) Date: Tue, 14 Dec 1999 01:53:37 +0000 (GMT) From: Alan Cox alan@lxorguk.ukuu.org.uk Subject: [Livid-dev] cvs: mpav > that. mutt doesn't make a good bug database :) I often wonder > how someone like Alan Cox can process _so_ much email and > remember which patch goes where and who it came from. I actually have a ludicrously simple system. Mail with sane bug reports and patches in I file in a directory called TODO with a version number attached. Mail without sane bug reports I bitbucket. I generally find that if you bitbucket a few similar emails it jogs your memory and you can fish them all out of the received folder to check. Alan