headers
Willats, Ian | 1 Mar 2005 12:41
Favicon

[p4] Tool to generate patch files from Perforce

Hello,

Is anyone aware of a tool or script that will allow UNIX patch files to
be generated from Perforce?  The main use case would be to choose a
directory in the depot and specify two revisions (changelist numbers,
labels, etc), at which point the tool would generate a patch file
describing the differences.  The output should be in a form that can be
used as input to the patch(1) command so that when applied to the
directory tree at the first revision, it would be updated to match the
second revision.

I know of p4 diff2 -du, which is close but has a couple of deficiencies
for this purpose.  Although the deficiencies are work-aroundable, I
would like to avoid re-inventing the wheel if possible!

Many thanks,

Ian

Ian Willats                         e-mail: ian.willats <at> windriver.com
Project Manager                     tel:    +44 (0)1564 711669
                                    fax:    +44 (0)1564 711302
Wind River UK Ltd
Central Boulevard, Blythe Valley Park, Solihull, B90 8AG, England

_______________________________________________
Come to the 2005 Perforce User Conference, April 14 & 15 in Las Vegas.
Learn more: http://www.perforce.com/conf 

perforce-user mailing list  -  perforce-user <at> perforce.com
(Continue reading)

Permalink | Reply | 2 comments |
headers
Peter Stephenson | 1 Mar 2005 13:02
Favicon

Re: [p4] Tool to generate patch files from Perforce

"Willats, Ian" wrote:
> I know of p4 diff2 -du, which is close but has a couple of deficiencies
> for this purpose.  Although the deficiencies are work-aroundable, I
> would like to avoid re-inventing the wheel if possible!

If you have a recent version of Perforce, you'll find that "p4 diff2 -u"
(no "d") gives a closer approximation to patch output.  I've found it's
good enough for me.

-- 
Peter Stephenson <pws <at> csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070

**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

**********************************************************************

_______________________________________________
Come to the 2005 Perforce User Conference, April 14 & 15 in Las Vegas.
Learn more: http://www.perforce.com/conf 

perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
(Continue reading)

Permalink | Reply | 0 comments |
headers
Fawad Khan | 1 Mar 2005 20:29

[p4] FW: Linux patch file generation

Is there an easy way to generate the following from Perforce?

 

Thanks,

Fawad

 

From: Yau Chu
Sent: Saturday, February 26, 2005 12:38 AM
To: Fawad Khan
Subject: Linux patch file generation

 

Fawad,

 

Here’s what I’d like to know:

 

How can I generate Linux patch files with Perforce on a directory that has been modified with file additions, file deletions, and edits?   There should be a patch file for each change list which affected the desired directory.  I should be able to apply the generated patch files on the set of files that was first checked into Perforce in order to re-create the current state of the directory.

 

I hope what I want is clearly expressed in the above description.

--

Yau

_______________________________________________
Come to the 2005 Perforce User Conference, April 14 & 15 in Las Vegas.
Learn more: http://www.perforce.com/conf 

perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 0 comments |
headers
Ken.Williams | 1 Mar 2005 21:18
Picon

RE: [p4] FW: Linux patch file generation

I don't know of any way to express a "file deletion" in a patch file.

The rest of the patch data can be easily generated by using "p4 diff2 -u ... <at> 1492 ...#have" in order to get a
patch between changelist 1492 and the currently synced version.

 -Ken

-----Original Message-----
From: perforce-user-bounces <at> perforce.com [mailto:perforce-user-bounces <at> perforce.com]On Behalf
Of Fawad Khan
Sent: Tuesday, March 01, 2005 1:30 PM
To: perforce-user <at> perforce.com
Subject: [p4] FW: Linux patch file generation

Is there an easy way to generate the following from Perforce?

Thanks,
Fawad

From: Yau Chu 
Sent: Saturday, February 26, 2005 12:38 AM
To: Fawad Khan
Subject: Linux patch file generation

Fawad,

Here's what I'd like to know:

How can I generate Linux patch files with Perforce on a directory that has been modified with file
additions, file deletions, and edits?   There should be a patch file for each change list which affected the
desired directory.  I should be able to apply the generated patch files on the set of files that was first
checked into Perforce in order to re-create the current state of the directory.

I hope what I want is clearly expressed in the above description.
--
Yau

_______________________________________________
Come to the 2005 Perforce User Conference, April 14 & 15 in Las Vegas.
Learn more: http://www.perforce.com/conf 

perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 1 comment |
headers
Nick Barnes | 2 Mar 2005 10:38
Picon
Favicon

Re: [p4] FW: Linux patch file generation

At 2005-03-01 20:18:59+0000, Ken.Williams <at> thomson.com writes:

> I don't know of any way to express a "file deletion" in a patch file.

diff -N (pretends absent files are present but empty) and patch -E
(remove any file which is empty after patch application).

Nick B
_______________________________________________
Come to the 2005 Perforce User Conference, April 14 & 15 in Las Vegas.
Learn more: http://www.perforce.com/conf 

perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 0 comments |
headers
Jason Williams | 2 Mar 2005 11:56

[p4] Soffront Track and Perforce

For any that might be interested, Soffront now offers Perforce integration with their Defect Tracking
system (and possibly with the other components of their system that use TrackWeb).

It sounds like they've integrated P4DTI with their product.

>From http://www.soffront.com/Newsletter/Feb2005/Feb2005.htm :
"Minimize the blocks that traditionally prevent productive communication between your development and
quality assurance groups. The Soffront Perforce integration is based on two way synchronization
between Trackweb defects and Perforce jobs to enhance information sharing among your team. It allows
Perforce change lists and related file names to be synchronized to the Trackweb database . 

>From Trackweb, you can view all the Perforce change list information and related file names for any
Trackweb defect. From within Perforce, you can see Trackweb defects as Perforce jobs. When you update any
Perforce job information, the changes will be available to Trackweb seamlessly, and vice versa. 

The integration also supports multiple Perforce servers and depots and effectively works within a
destributed environment."

--Jason

_______________________________________________
Come to the 2005 Perforce User Conference, April 14 & 15 in Las Vegas.
Learn more: http://www.perforce.com/conf 

perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 0 comments |
headers
Ken.Williams | 2 Mar 2005 16:11
Picon

RE: [p4] FW: Linux patch file generation

Ah, good to know.  Thanks.

 -Ken

> -----Original Message-----
> From: nb <at> ravenbrook.com [mailto:nb <at> ravenbrook.com]On Behalf Of Nick
> Barnes
> Sent: Wednesday, March 02, 2005 3:39 AM
> To: Williams, Ken (TLR Corp)
> Cc: FawadKhan <at> airgonetworks.com; perforce-user <at> perforce.com
> Subject: Re: [p4] FW: Linux patch file generation 
> 
> 
> At 2005-03-01 20:18:59+0000, Ken.Williams <at> thomson.com writes:
> 
> > I don't know of any way to express a "file deletion" in a 
> patch file.
> 
> diff -N (pretends absent files are present but empty) and patch -E
> (remove any file which is empty after patch application).
> 
> Nick B
> 

_______________________________________________
Come to the 2005 Perforce User Conference, April 14 & 15 in Las Vegas.
Learn more: http://www.perforce.com/conf 

perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 2 comments |
headers
Zarnes, Todd | 2 Mar 2005 20:24
Picon

[p4] Security=1

With Security set to ‘1’ on Perforce is there anyway to open the instance to read only without the need for a password?  I installed P4Web and was trying to setup maven to read the instance without having to login.

 

Todd  Zarnes

Eclipse SCM

 

_______________________________________________
Come to the 2005 Perforce User Conference, April 14 & 15 in Las Vegas.
Learn more: http://www.perforce.com/conf 

perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 0 comments |
headers
Grills, Jeff | 2 Mar 2005 21:04
Picon

RE: [p4] Security=1

We use a "background user", an account that is for the purpose of scripting which no human will ever use (except to set up the automated scripts and stuff, of course).  We put that user into its own group and assign the group a very long ticket time and issue a p4 login once to obtain the ticket that it can use basically forever.  That way the password never needs to be stored on the machine, but it can still access perforce as necessary.  This works with higher security levels as well.
 
Hopefully this will help.
 
j
-----Original Message-----
From: perforce-user-bounces <at> perforce.com [mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Zarnes, Todd
Sent: Wednesday, March 02, 2005 1:25 PM
To: perforce-user <at> perforce.com
Subject: [p4] Security=1

With Security set to ‘1’ on Perforce is there anyway to open the instance to read only without the need for a password?  I installed P4Web and was trying to setup maven to read the instance without having to login.

 

Todd  Zarnes

Eclipse SCM

 

_______________________________________________
Come to the 2005 Perforce User Conference, April 14 & 15 in Las Vegas.
Learn more: http://www.perforce.com/conf 

perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 0 comments |
headers
Brian Moyers | 4 Mar 2005 00:56

[p4] Job Openings at BEA Systems

Hello, we've got one position open in San Jose, CA and two open 
positions in Burlington, MA.  See job description below and send resumes 
to me (bmoyers at bea.com) in text or pdf format for review.  If you 
meet the qualifications listed below and are interested in working in a 
large Perforce shop, focusing on ANT and CruiseControl, we'd be happy to 
hear from you.

-------------------------------

SR. INFRASTRUCTURE ENGINEER

Major Duties and Responsibilities:

The candidate will define, create and maintain automated tools to: 
facilitate code check-ins for software engineers and for product releases.

Senior Infrastructure Engineer is expected to be self-motivated, be able 
to research technology, specify features, estimate and schedule tasks, 
as well as complete tasks in a timely manner and also be able to lead 
and/or mentor other team members to a successful objective completion.

Qualifications/Necessary Skills:

3-5 years of experience in the field.    Strong background on software 
release management, configuration management and source code management. 

Critical success factors for this position are:  Individual should be 
self-motivated, work well under pressure, and be able to work towards 
aggressive deadlines and be able to communicate clearly and concisely. 
    Experience with different source code management models and 
methodology; single source, multiple branches...

Functional success factors:  Knowledge in source code management 
systems, Perforce a plus.  Background in UNIX, XP/NT/WIN2K, Makefiles, 
ANT,  InstallAnywhere, HTTP, PERL and scripting language, and 
familiarity with Java.  Familiarity with CruiseControl a plus.

Educational Requirements:

B.S. in Computer Science or related field is required

--

-- 
Brian Moyers
Sr. Software Engineer
BEA Systems
bmoyers at bea.com
_______________________________________________
Come to the 2005 Perforce User Conference, April 14 & 15 in Las Vegas.
Learn more: http://www.perforce.com/conf 

perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 0 comments |

Gmane