1 message in com.perforce.perforce-user[p4] Re:perforce-user digest, Vol 1 #...
FromSent OnAttachments
Thatcher Deane23 Nov 2001 12:05 
Subject:[p4] Re:perforce-user digest, Vol 1 #690 - 3 msgs (Vacation Alert)
From:Thatcher Deane (That@ci.seattle.wa.us)
Date:11/23/2001 12:05:29 PM
List:com.perforce.perforce-user

I am on vacation beginning Tue Nov 20th returning Fri Nov 30th. In my absence .....

* Source Code and Change Management --> Vic Koenig 684-0952 * DoIT / AIX Single point of contact --> Jose Torres 386-4547 * CCSS Web maintenance --> Son Nguyen 615-1134 * Maintenance outage coordination --> Bruce Raymond 615-1160

ALSO:

* SCL IT support for BOC: SCL Service Desk: 684-3766

* AIX admin durring business hours: Philip Yu 684-3690

* AIX problems off hours: Computer Center Operations 3-5050

* CCSS Status Hotline 233-7900

-Thatcher Deane CCSS Infrastructure Lead

"perforce-user at perforce.com" 11/23/01 12:05 >>>

Send perforce-user mailing list submissions to perforce-user at perforce.com

To subscribe or unsubscribe via the World Wide Web, visit http://maillist.perforce.com/mailman/listinfo/perforce-user or, via email, send a message with subject or body 'help' to perforce-user-request at perforce.com

You can reach the person managing the list at perforce-user-admin at perforce.com

When replying, please edit your Subject line so it is more specific than "Re: Contents of perforce-user digest..."

Today's Topics:

1. Re:perforce-user digest, Vol 1 #689 - 1 msg (Vacation Alert) (Thatcher
Deane) 2. An Update Problem (Karl Philipp) 3. Re: An Update Problem (Stephen Vance)

--__--__--

Message: 1 Date: Thu, 22 Nov 2001 12:06:06 -0800 From: "Thatcher Deane" <Thatcher.Deane at ci.seattle.wa.us> Reply-To: Thatcher.Deane at ci.seattle.wa.us To: <perforce-user at perforce.com> Subject: [p4] Re:perforce-user digest, Vol 1 #689 - 1 msg (Vacation Alert)

I am on vacation beginning Tue Nov 20th returning Fri Nov 30th. In my absence .....

* Source Code and Change Management --> Vic Koenig 684-0952 * DoIT / AIX Single point of contact --> Jose Torres 386-4547 * CCSS Web maintenance --> Son Nguyen 615-1134 * Maintenance outage coordination --> Bruce Raymond 615-1160

ALSO:

* SCL IT support for BOC: SCL Service Desk: 684-3766

* AIX admin durring business hours: Philip Yu 684-3690

* AIX problems off hours: Computer Center Operations 3-5050

* CCSS Status Hotline 233-7900

-Thatcher Deane CCSS Infrastructure Lead

"perforce-user at perforce.com" 11/22/01 12:05 >>>

Send perforce-user mailing list submissions to perforce-user at perforce.com

To subscribe or unsubscribe via the World Wide Web, visit http://maillist.perforce.com/mailman/listinfo/perforce-user or, via email, send a message with subject or body 'help' to perforce-user-request at perforce.com

You can reach the person managing the list at perforce-user-admin at perforce.com

When replying, please edit your Subject line so it is more specific than "Re: Contents of perforce-user digest..."

Today's Topics:

1. Re:perforce-user digest, Vol 1 #688 - 2 msgs (Vacation Alert) (Thatcher
Deane)

-- __--__--

Message: 1 Date: Wed, 21 Nov 2001 12:05:20 -0800 From: "Thatcher Deane" <Thatcher.Deane at ci.seattle.wa.us> Reply-To: Thatcher.Deane at ci.seattle.wa.us To: <perforce-user at perforce.com> Subject: [p4] Re:perforce-user digest, Vol 1 #688 - 2 msgs (Vacation Alert)

I am on vacation beginning Tue Nov 20th returning Fri Nov 30th. In my absence .....

* Source Code and Change Management --> Vic Koenig 684-0952 * DoIT / AIX Single point of contact --> Jose Torres 386-4547 * CCSS Web maintenance --> Son Nguyen 615-1134 * Maintenance outage coordination --> Bruce Raymond 615-1160

ALSO:

* SCL IT support for BOC: SCL Service Desk: 684-3766

* AIX admin durring business hours: Philip Yu 684-3690

* AIX problems off hours: Computer Center Operations 3-5050

* CCSS Status Hotline 233-7900

-Thatcher Deane CCSS Infrastructure Lead

"perforce-user at perforce.com" 11/21/01 12:05 >>>

Send perforce-user mailing list submissions to perforce-user at perforce.com

To subscribe or unsubscribe via the World Wide Web, visit http://maillist.perforce.com/mailman/listinfo/perforce-user or, via email, send a message with subject or body 'help' to perforce-user-request at perforce.com

You can reach the person managing the list at perforce-user-admin at perforce.com

When replying, please edit your Subject line so it is more specific than "Re: Contents of perforce-user digest..."

Today's Topics:

1. Re: Make "standard header files" NOT expand RCS keywords? (Arnt
Gulbrandsen) 2. new cm website (Sally.Page at symbian.com)

-- __--__--

Message: 1 Date: Mon, 19 Nov 2001 20:04:01 +0100 From: Arnt Gulbrandsen <arnt at gulbrandsen.priv.no> To: Dave Lewis <dlewis at vignette.com> Cc: david.karr at cacheflow.com, perforce-user at perforce.com Subject: Re: [p4] Make "standard header files" NOT expand RCS keywords?

Dave Lewis <dlewis at vignette.com>

I believe its off by default. I think a p4 fstat on the file will tell you if it is on or not.

Perhaps, but it used to be on, if my memory serves me correctly.

We were using p4 on an intercontinental link. Ten time zones from client to server. For some reason submits were far too slow, and IIRC the problem was keyword expansion, which was on by default. "p4 edit -t text" on all of our .cpp and .h files speeded that up nicely.

--Arnt

-- __--__--

Message: 2 From: Sall@symbian.com To: perforce-user at perforce.com Date: Wed, 21 Nov 2001 11:45:12 +0000 Subject: [p4] new cm website

quite a useful new site :

http://www.snuffybear.com/ucmcentral.htm

Sally Page Configuration Management Engineer Symbian (UK) Ltd Direct: 020 7563 2912 Mobile: 07769 588915

********************************************************************** Symbian Ltd is a company registered in England and Wales with registered number
01796587 and registered office at 19 Harcourt Street, London, W1H 4HF, UK. This message is intended only for use by the named addressee and may contain
privileged and/or confidential information. If you are not the named addressee
you should not disseminate, copy or take any action in reliance on it. If you
have received this message in error please notify postmaster at symbian.com and
delete the message and any attachments accompanying it immediately. Symbian does
not accept liability for any corruption, interception, amendment, tampering or
viruses occurring to this message in transit or for any message sent by its
employees which is not in compliance with Symbian corporate policy. **********************************************************************

-- __--__--

_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user

End of perforce-user Digest

-- __--__--

_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user

End of perforce-user Digest

--__--__--

Message: 2 From: "Karl Philipp" <karl.philipp at danet.de> To: "Mailinglist Perforce User" <perforce-user at perforce.com> Date: Fri, 23 Nov 2001 17:04:35 +0100 Subject: [p4] An Update Problem

Hi,

A vendor delivered last week:

SS_OE.doc (Version 2)

Now the vendor has delivered:

SS_OE.pdf (Version 3)

That is the recent delivered version has another type: PDF

How can I update the old version with the new version?

IMO, the described approach on Perforce's web-site (p4 rename) doesn't work properly in this case, because the lazy branching method creates a new version that is not really a pdf file but the last doc file.

Any other idea?

so long

Karl

--- Karl Philipp

Phone : +49 6151 868 - 518 Fax : +49 6151 868 - 980 eMail : mailto:karl.philipp at danet.de

Danet GmbH, Business Unit BI Gutenbergstr. 10 64331 Weiterstadt, Germany WWW : http://www.danet.de

--__--__--

Message: 3 Date: Fri, 23 Nov 2001 12:07:01 -0500 To: "Karl Philipp" <karl.philipp at danet.de>, "Mailinglist Perforce User" <perforce-user at perforce.com> From: Stephen Vance <steve at vance.com> Subject: Re: [p4] An Update Problem

I would just delete the old one and add the new one. The old one may serve the same function and have the same logical content, but is a different packaging and physical form. If you play games to make the history of the PDF flow directly into the DOC, you are essentially stating they are the same thing at different revisions. This is true from a logical perspective ("It's the documentation"), but not from a CM perspective. Just ask yourself the question, "How would I handle it if they gave the docs in two or more formats (e.g. HTML, PDF, DOC, PS)?"

At 05:04 PM 11/23/2001 +0100, Karl Philipp wrote:

Hi,

A vendor delivered last week:

SS_OE.doc (Version 2)

Now the vendor has delivered:

SS_OE.pdf (Version 3)

That is the recent delivered version has another type: PDF

How can I update the old version with the new version?

IMO, the described approach on Perforce's web-site (p4 rename) doesn't work properly in this case, because the lazy branching method creates a new version that is not really a pdf file but the last doc file.

Any other idea?

so long

Karl

Danet GmbH, Business Unit BI Gutenbergstr. 10 64331 Weiterstadt, Germany WWW : http://www.danet.de

Stephen Vance mailto:steve at vance.com http://www.vance.com/

--__--__--

End of perforce-user Digest