Date: Sun, 1 Jan 95 2:47:32 MET From: phk@login.dknet.dk (Poul-Henning Kamp) To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: bde@freefall.cdrom.com, CVS-commiters@freefall.cdrom.com, cvs-gnu@freefall.cdrom.com Subject: Re: cvs commit: src/gnu/usr.bin/gdb/bfd sysdep.h Message-ID: <9501010147.AA20820@login.dknet.dk> In-Reply-To: <26682.788893355@time.cdrom.com>; from "Jordan K. Hubbard" at Dec 31, 94 9:02 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > cvs is not being used effectively for gdb. Our old changes get clobbered > > and our new changes are mixed with "vendor" changes in the same updates > > so they will be difficult to untangle for the next release of gdb. The > > revision logs get spammed for each release of gdb. > > Sorry about that. I'm not a CVS expert by a long shot, and so I'd welcome > any suggestions as to how better to do this in the future. I believe we > have the same kinds of trouble with groff, gcc, etc.. We need to make a decision on all the GNU stuff. The problem exists for all of the gnu sources, if for nothing else then because of the bmake principle. We need a traceable method to come from a gnu-dist to a bmake tree. I tried with the gnu2bmake stuff, but faced opposition, so I'm sitting tight just now, waiting for the alternative to appear... Happy 1995 ! Poul-Henning
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9501010147.AA20820>