11 messages in com.perforce.perforce-user[p4] dry-run mode for edit, delete, a...| From | Sent On | Attachments |
|---|---|---|
| Wolcott, Kenneth | 24 May 2001 16:52 | |
| Dave Lewis | 24 May 2001 19:35 | |
| Wolcott, Kenneth | 24 May 2001 20:05 | |
| Paul Goffin | 25 May 2001 00:24 | |
| Robert Cowham | 25 May 2001 00:33 | |
| Gregg G. Wonderly | 25 May 2001 05:58 | |
| ste...@vance.com | 25 May 2001 07:13 | |
| Hamish Macdonald | 25 May 2001 08:30 | |
| Trent Mick | 25 May 2001 09:15 | |
| Wolcott, Kenneth | 25 May 2001 15:45 | |
| Wolcott, Kenneth | 25 May 2001 15:51 |
| Subject: | [p4] dry-run mode for edit, delete, add like there is for syn c? |
|---|---|
| From: | Wolcott, Kenneth (KWol...@DigitalArchway.com) |
| Date: | 05/24/2001 08:05:19 PM |
| List: | com.perforce.perforce-user |
Hi Dave;
I have the following scenario:
1> a cd-rom full of files is brought into perforce from the outside (new files): no problem; 2> later another cd-rom full of files comes in with zero or more new files and/or zero or more deleted files and/or zero or more changed files (no information about what file(s) have changed); 3> I placed a label on the first set of files; 4> now I need to incorporate the new set of files on top of the prior label accurately; 5> now make a new label;
So I used windiff to get a listing of the new files, old files, identical files and changed files. Then I'll p4 delete the old files, p4 edit the changed files, copy just the new and changed files over, p4 add the new files and then p4 submit the whole thing.
Do you have a better suggestion?
Meanwhile, I "cheated". I just checked in the new stuff in a sibling directory.
Ken
-- Kenneth A. Wolcott SMTS - SCM Engineer kwolcott at digitalarchway.com
-----Original Message----- From: Dave Lewis [mailto:dlewis at vignette.com] Sent: Thursday, May 24, 2001 7:36 PM To: KWolcott at DigitalArchway.com Cc: perforce-user at perforce.com Subject: Re: [p4] dry-run mode for edit, delete, add like there is for sync?
> From: "Wolcott, Kenneth" <KWolcott at DigitalArchway.com> > > It would be really nice if there was a "dry-run" flag for "p4 edit", "p4 > delete" and "p4 add" like there is for "p4 sync". I know that the changes I > make via the edit, delete and add commands aren't permanent until I run "p4 > submit", but I'd rather not have to revert changes unneccessarily.
I'm having a hard time trying to understand this. the best I can do is figure that you are using wildcards and don't know what the scope of some of the commands might do... Otherwise I wonder why p4 edit file p4 delete file p4 add file would need any kind of preview.
given its the wildcard issue, you could do a p4 files '//depot/whatever/.../*patt*.cpp' or whatever to see what files might be affected.
dave