[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Syd Polk <spolk@redhat.com>] cvs import

From: Jim Blandy <jimb_at_zwingli.cygnus.com>
Date: 2000-10-13 01:14:46 CEST

What he said.

------- Start of forwarded message -------
Message-Id: <4.2.0.58.20001009173305.00dc58b0@pop.cygnus.com>
Date: Mon, 09 Oct 2000 17:35:49 -0700
To: Jim Blandy <jimb@cygnus.com>
From: Syd Polk <spolk@redhat.com>
Subject: cvs import

OK, I hate cvs import.

I am sure that for the purpose it was intended, it is great. Get new source
to a package you don't modify, import it and it is on the head, and
everything is hoopy.

However, trying to import to a branch sucks.

First, you have to do a dummy commit.
Then you import.
After you import, you remove all of the new files the package added.
Then you can do your merge and commit.

The big win with cvs import is the 3-way merge is made easy. But forgetting
these other steps just causes much mayhem.

I thought you might be interested in my frustration as I busily remove
about 50 files I accidentally added to devo several months ago in devo/itcl.

Syd Polk spolk@redhat.com
Engineering Manager +1 415 777 9810 x 241
Red Hat, Inc.

------- End of forwarded message -------
Received on Sat Oct 21 14:36:10 2006

This is an archived mail posted to the Subversion Dev mailing list.