Date: Tue, 23 May 2000 23:05:18 -0700 From: "Andrey A. Chernov" <ache@freebsd.org> To: Peter Wemm <peter@netplex.com.au> Cc: Bill Fumerola <billf@chc-chimes.com>, David O'Brien <obrien@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/contrib/ncurses/include curses.h.in src/contrib/ncurses/ncurses/trace lib_trace.c Message-ID: <20000523230517.A31796@freebsd.org> In-Reply-To: <20000524040639.3A14D1CE1@overcee.netplex.com.au>; from peter@netplex.com.au on Tue, May 23, 2000 at 09:06:39PM -0700 References: <ache@FreeBSD.org> <20000524040639.3A14D1CE1@overcee.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 23, 2000 at 09:06:39PM -0700, Peter Wemm wrote: > The issue isn't fixing the problem, the issue is how you did it. With a > little care you can have it fixed properly without messing up the cvs files. I understand what you say here about messing up the cvs files, but lets try to think from another point of view: we have branches to make changes (commits and backing outs) easy, not branches have us and force us to stay away due some inefficency of cvs as a tool. CVS file is just a text file and any of its previous state can be resored easily in theory (at least restoring from backup copy does this). What I am trying to say: we need a tool for TRUE back out, i.e. back out removing branches too, maybe perl script or something alike. BTW, do you plan to commit official fix in near time by yourself? If you are busy I can do after clean backing out of my changes. -- Andrey A. Chernov <ache@nagual.pp.ru> http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000523230517.A31796>