This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: commitinfo script to check policy, issue warnings (and/or abort commit)
- To: gcc at gcc dot gnu dot org
- Subject: Re: commitinfo script to check policy, issue warnings (and/or abort commit)
- From: Marc Espie <espie at quatramaran dot ens dot fr>
- Date: Wed, 16 May 2001 22:31:10 +0200
- Organization: Ecole Normale Superieure (quatramaran)
import is all very fine in theory. There are two large stumbling blocks
though, which make it VERY annoying.
* the cvs program is a complete nitwit when it comes to merging stuff imported
on vendor branches. It's very good at resurrecting stuff that's been
completely forgotten about, and that you eradicated yourself. The suggestions
it gives for facilitating the merge are erroneous at best.
* cvs can't import to anything but HEAD.
* cvs can't import to anything but HEAD.
* cvs can't import to anything but HEAD.
* cvs can't import to anything but HEAD.
The first issue is already a large pain. I've been routinely using vendor
branches to import gcc/gdb/binutils to OpenBSD, and believe me, it's a real
pain, thanks to the size of those projects (try bringing back the testsuite
from 2.8 when it isn't include in 2.95, for instance, or go on removing
umpteen files that have been eradicated since then and that `import' insists
on bringing back to life.
The second issue is completely brain-dead. It just means that in many cases,
you have the choice of creating an entire new tree for experimental work,
or forgetting about import entirely.
Trying to do advanced things with cvs is likely to bring major pain. There is
no decent free alternative right now, but getting cute with cvs is a MAJOR
loss...
This is just a warning...