10 messages in com.perforce.revml[revml] Mirroring CVS archives into P...| From | Sent On | Attachments |
|---|---|---|
| Gary Tomic | 30 Jan 2002 12:04 | |
| Barrie Slaymaker | 31 Jan 2002 08:40 | |
| Gary Tomic | 31 Jan 2002 10:01 | |
| rm...@perforce.com | 31 Jan 2002 10:39 | |
| Chuck Karish | 31 Jan 2002 11:20 | |
| Barrie Slaymaker | 31 Jan 2002 11:33 | |
| Gary Tomic | 01 Feb 2002 09:46 | |
| Gary Tomic | 01 Feb 2002 09:49 | |
| Gary Tomic | 01 Feb 2002 10:20 | |
| rm...@perforce.com | 01 Feb 2002 12:21 |
| Subject: | [revml] Mirroring CVS archives into Perforce |
|---|---|
| From: | Barrie Slaymaker (barr...@slaysys.com) |
| Date: | 01/31/2002 11:33:43 AM |
| List: | com.perforce.revml |
On Thu, Jan 31, 2002 at 01:02:21PM -0500, Gary Tomic wrote:
From: "Barrie Slaymaker" <barr...@slaysys.com>
Using cvs2p4, I can specify the branch names that I want to import, so that is probably be the best way to start.
Agreed. What I meant to ask was how you (personally, in this situation) would specify the source revisions to cvs for the later, incremental update you'd do with vcp to bring the tracking depot up to date.
I don't know the repository you're reading from and would like to see what cvs options you'd use to get the logs for just the files and revisions needed for the incremental update. That way I can make sure that any tweaks I need to do to VCP::Source::cvs will work for you.
I would agree with your assesment. It is probably better to go from //mydepot back to opensource and bring the changes back using vcp into the //opensource depot. Using Perforce with Araxis Merge is good at catching these things, and will do the correct thing (not double copy) when merging from //opensource to //mydepot when the change is already present.
I'd like vcp to do the right thing there too. does Araxis merge make it look like the user did a p4 resolve?
- Barrie