8 messages in com.perforce.revml[revml] Perforce -> CVS mirror| From | Sent On | Attachments |
|---|---|---|
| Thomas Quinot | 14 Jan 2002 02:04 | |
| Barrie Slaymaker | 14 Jan 2002 08:15 | |
| Thomas Quinot | 14 Jan 2002 09:32 | |
| Barrie Slaymaker | 14 Jan 2002 11:24 | |
| Thomas Quinot | 15 Jan 2002 04:41 | |
| Thomas Quinot | 15 Jan 2002 08:57 | |
| Barrie Slaymaker | 15 Jan 2002 10:23 | |
| Barrie Slaymaker | 15 Jan 2002 10:45 |
| Subject: | [revml] Perforce -> CVS mirror |
|---|---|
| From: | Barrie Slaymaker (barr...@slaysys.com) |
| Date: | 01/14/2002 11:24:56 AM |
| List: | com.perforce.revml |
On Mon, Jan 14, 2002 at 06:32:44PM +0100, Thomas Quinot wrote:
< -- $Id: //droopi/main/src/droopi-soft_links.ads#1 $
---
-- $Id: droopi-soft_links.ads,v 1.1 2002/01/14 10:03:12 quinot Exp $
Bingo, thanks.
I'm quite available to work on this with you and I really want to get this working.
I think one possible course of action here would be to allow post-processing every checkout from Perforce by substituting any '$Id:' with e.g. '$Perforce:'.
That way: * no more differences between source and dest file (because no further substitution will occur); * as an additional benefit, you can immediately identify the Perforce revision that corresponds to a given checked-out file obtained from CVS, without having to refer to the label.
I like the second feature, however this approach means that if you're doing a p4->cvs one time import, you neuter the tags so CVS can no longer expand them for you.
I don't want to alter the files at all. I can live with carriage return mangling to deal with portability issues, but this is content alteration.
I'll have to do the checkouts from both without keyword expansion.
- Barrie