9 messages in com.perforce.perforce-user[p4] NT Users Survey
FromSent OnAttachments
Tal Dayan24 Jan 2000 08:48 
Piaw Na24 Jan 2000 13:58 
Dave Birkhead24 Jan 2000 14:11 
Short, Todd24 Jan 2000 14:24 
Martin Ellison24 Jan 2000 14:25 
Ted Eiles24 Jan 2000 14:29 
Jonathan Arnold24 Jan 2000 14:49 
Scott Blachowicz24 Jan 2000 17:40 
Yariv Sheizaf24 Jan 2000 23:11 
Subject:[p4] NT Users Survey
From:Dave Birkhead (dav@extensity.com)
Date:01/24/2000 02:11:10 PM
List:com.perforce.perforce-user

For automation I use the Command line for day to day operations I use both about 50%, 50%

-----Original Message----- From: Tal Dayan [mailto:tal at zapta.com] Sent: Monday, January 24, 2000 8:49 AM To: Perforce List Subject: [p4] NT Users Survey

This question is to the Perforce/NT users among us.

Which of Perforce's interfaces do you use most of the time, the text based or the GUI ?

I am using the text interface for 95% of the time, except for creating users, clients, etc.

Tal

-----Original Message----- From: perforce-user-admin at perforce.com [mailto:perforce-user-admin at perforce.com]On Behalf Of Bert Lindgren Sent: Tuesday, September 21, 1999 2:18 PM To: Mike Meyer Cc: Perforce List Subject: Re: [p4] "Integrate" to same file?

What about using a sandbox branch to submit all the changes and then integrating to the desired 'real' branch where you can pick-and-choose the actual submissions?

Just a thought, Bert

Mike Meyer wrote:

On Thu, 16 Sep 1999, Steve Cogorno wrote: :->Basically, I would like to get an editable diff of the file that looks like :->the resolve output. Example: :-> :->>>>> ORIGINAL :-><e-i-c gi="caution-note.fmt"><?Pub Lcl _id="f1757"><?Pub Dtl> :->==== YOURS :-><e-i-c gi="caution-note.fmt"><?Pub Lcl _id="f1757"> :-><<<<

It wouldn't solve your problem, but an option to get that output from diff or diff2 would be a nice enhancement. Well - it would make your problem easier to deal with.

:->I want to be able to review the changes and reject some of them before :->submitting the files. I can do this with diff, but it isn't very :->convenient, because I can't edit the merged files. :-> :->Before you say "Well don't change the file if you don't want to keep the :->changes" let me explain. These files are actually edited through a GUI, and :->the tool inserts line changes that are irrelevent. Sometimes the line :->breaking will change, or a "<?Pub Dtl>" will get added. These don't change :->the meaning of the files at all. But what it does do is cause more manual :->conflicts later on when I have to integrate the changes into another branch.

Are these changes random, so that dealing with them once won't solve the problem?

When you say the word "review", I tend to think of two branches - one that's edited and then reviewed, and a second that the reviewed versions are integrated into after they are approved. Would something like that work?

<mike