[p4] unsubscribe perforce-user

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user

RE: [p4] Proxy could not update its cache Error

The Proxy machine has an 8GB hard drive, with 5GB free, so the problem is
not a lack of diskspace. (The files failing to cache are only a few Kb in
size)

Running with -ZproxyVerbose gives the same error.

-----Original Message-----
From: Robert Cowham [mailto:robert <at> vaccaperna.co.uk]
Sent: 30 November 2004 16:57
To: 'Oliver, Jonathan'; perforce-user <at> perforce.com
Subject: RE: [p4] Proxy could not update its cache Error

               *** WARNING ***

This mail has originated outside your organization,
either from an external partner or the Global Internet. 
     Keep this in mind if you answer this message. 

Is the cache full? Has it run out of disk space?

If so, then just delete a chunk of files - they will be replaced as and when
used.

Robert 

> -----Original Message-----
> From: perforce-user-admin <at> perforce.com 
> [mailto:perforce-user-admin <at> perforce.com] On Behalf Of 
> Oliver, Jonathan

[p4] Problem: Sync to head revision with files checked out

Hi all
I have this problem
When I have some files opened for write in machine A and try to force 
sync to head revision and machine B, I can't get the opened for write 
files at all at machine B.

After sumbitting the files in machine A, I can get the files at machine B.

Is there a client/depot setting that I miss?

Regards

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

[p4] webkeeper precompiled module

Has a precompiled webkeeper module, and sample config, for Apache 2.0.50 running
on windows, been posted anywhere?  I'm a little Daunted by the readme instructions
for getting it compiled and setup, and being lazy (er I mean mindful of my
resources) was wondering if anyone had already done that work for the rest
of the community...

On a related note, is webkeeper considered the best
http implementation for just straight old http read access to the contents
of a repository?  We want to be able to ship arround urls that look like this

http://our.perforce.server.com/p4-docs/readme.txt

where p4-docs is a
depot, and that link will always return the head of the document.

the URL
structure that comes out of the p4web is not terribly friendly for the non
development staff who need to review documents that are tracked in Perforce.

Thanks
Dan Weatbrook
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user

[p4] Perforce Integration with Quest TOAD

RE: [p4] Problem: Sync to head revision with files checked out

> -----Original Message-----
> From: Hesham Desouky [mailto:hesham_d <at> link.net]
> 
> Hi all
> I have this problem
> When I have some files opened for write in machine A and try to force 
> sync to head revision and machine B, I can't get the opened for write 
> files at all at machine B.
> 
> After sumbitting the files in machine A, I can get the files 
> at machine B.
> 
> Is there a client/depot setting that I miss?

Sounds like you're trying to use the same client on both
machines. The state of the files is tracked by client,
so Perforce knows you have those files checked out and
won't overwrite them. (It doesn't know you've switched
machines and/or filesystems.) Solution is to create a
second client for machine B, using the first client as
a template.

-Wm

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

Re: [p4] Perforce Integration with Quest TOAD

I have used it before with TOAD 7.6.0.11 (older version).  For that version
go to View-->Options...-->Team Coding

Probably similar for more recent versions.

Tommy

                                                                           
             Ilya Rokhkin                                                  
             <r_ilya <at> barak.net                                             
             .il>                                                       To 
             Sent by:                  perforce-user <at> perforce.com          
             perforce-user-adm                                          cc 
             in <at> perforce.com                                               
                                                                   Subject 
                                       [p4] Perforce Integration with      
             12/01/2004 11:06          Quest TOAD                          
             AM                                                            

Hello.

Does anybody integrated Perforce with Quest TOAD?
If Yes please advise how to integrate them.

With best regards.
Ilya Rokhkin        ilya <at> direct-solution.com
Application Engineer.
Direct Solution Ltd., Israel
Tel: (972)-9-7687888
Mobile: (972)-54-4560023
Fax: (972)-9-7687999

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

Re: [p4] Problem: Sync to head revision with files checked out

"Ivey, William" <william_ivey <at> bmc.com> writes:
> Sounds like you're trying to use the same client on both
> machines. The state of the files is tracked by client,

I thought that might have been his problem, too.  On a second read, though, I
think that he just doesn't understand that there is no new head revision on
the server for machine B to sync to until Machine A's client submits it.
--

-- 
g. matthew rice <matt <at> starnix.com>           starnix, toronto, ontario, ca
phone: 647.722.5301 x242                                  gpg id: EF9AAD20
http://www.starnix.com              professional linux services & products
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user

RE: [p4] the problems of migrating due to competing keywords ...

> Hello all.
> 
> I'm in the process of migrating my code from my old SCM to Perforce
> (yea!).  What I'm doing is taking about a dozen important 
> snapshots from
> my old system, and then adding them to perforce.
> 
> The problem is in the keyword substitution.  I don't know if I can
> explain it, so I'll example it.
> 
> Lets say I've got too files a.c and b.c.  Both have the 
> Revision keyword
> in their comments.  Now, in the first snapshot that I export 
> from my old
> system, both a.c and b.c are version 10.  So, I check them into
> Perforce.  In P4, they now have revision 1.  This makes sense to me.
> Now, I check out my second snapshot from the old SCM.  In 
> this snapshot,
> a.c hasn't changed (revision 10) and b.c has (revision 11).  
> Now, when I
> ask P4 to find the files that have changed, of course it thinks that
> both a.c and b.c have changed.  (It thinks a.c has changed due to the
> fact that a diff performed on it returns a delta.)
> 
> Should I just resign myself to the fact that perforce is 
> going to think
> that in every snapshot I'm migrating that everything has changed?  Or,
> is there a way to tell perforce that if a file's contents have changed
> only in the area of it's keyword substitution area, that it really
> hasn't changed?
> 
> Thanks.

Well, with all your help, I've come up with a workable solution.
Basically, it's a script that parses the output of the 'p4 diff -se'
command, then performs an external diff on the file ignoring anything
that matches the regular expression "$(Id|Revision|Date|Author).*$".
The files that are remaining are files that actually have a difference.

I've attached my script below in case others might find it useful in the
future.  

Again, thanks for all your suggestions.

----------------- find_p4_diff ------------------------
#!/usr/bin/bash
# 
# Tries to find all commands that have been modified but are not
existing
# in a change list, where the changes are more then just revision number
# changes.
#
# note: the P4DIFF variable needs to be set to the GNU diff command,
using
# the 'ignore reg ex' parameter.  Something like this:
#   p4 set P4DIFF="diff --ignore-matching-lines=$Revision:"

p4 set P4DIFF="diff
--ignore-matching-lines='\$\(Header\|Revision\|Author\|Date\|Id\).*\$'"

# find all files that have been modified but are not in the change list
for filename in `p4 diff -se`
do
    # for a specific file ...
    # diff the file and ignore the P4 diff header (starting with "====")
    diff_output=`p4 diff -f ${filename} | grep -v "^===="`
    # if the resulting output of the diff command is not empty ...
    if [ -n "$diff_output" ]
    then
        # open this file for editing
        p4 edit $filename
        #echo "opening for edit $filename"
        #echo "${diff_output}"
    else
        echo "skipping $filename as it's only revision different"
    fi
done

----------------- find_p4_diff ------------------------

--
Jay Glanville

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

Re: [p4] webkeeper precompiled module

--- joeblough54.2855795 <at> bloglines.com wrote:

> 
> On a related note, is webkeeper considered the best
> http implementation for just straight old http read access to the
> contents
> of a repository?  We want to be able to ship arround urls that look
> like this
> 
> 
> http://our.perforce.server.com/p4-docs/readme.txt
> 
> where p4-docs is a
> depot, and that link will always return the head of the document.
> 

I created DNS entries for each depot name pointing to the server, so
that you can just use simple copy-paste from the client (Windows) then
only have to prepend "http:"

  http: + //depot/branch/readme.txt

  where "depot" resolves to server (i.e., [10.10.10.199]
depot.domain.com)

probably tweaked some vitrual host settings too, don't remember now.

-- Dennis

> 
> Thanks
> Dan Weatbrook
> 

	
		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user