Tetlow, Gordon | 1 Feb 01:24 2005
Picon

RE: [p4] Client spec help needed

p4 help undoc:

 

    + mappings

        A mapping line that begins with + does not mask lower precedent

        mappings so that, for example, it is possible to map multiple

        server directories to the same client directory in the client

        view.  The support for this is only partial, in that if two

        server files end up mapping to the same client file, the 'p4

        sync' command will repeatedly replace one file with another.

 

Try the following:

 

+//SharedLib/maindev/delphi/subdir/GTIGDI/* //myclient/*
+//SharedLib/maindev/delphi/subdir/Help/* //myclient/*


 

From: perforce-user-bounces <at> perforce.com [mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Libby, Cynthia
Sent: Monday, January 31, 2005 12:04 PM
To: 'perforce-user <at> perforce.com'
Subject: [p4] Client spec help needed

 

We have a directory in perforce with multiple subdirectories. We want to map two of those directories into one directory and ignore the others. Since the client spec lines build upon each other I can't figure out how to do this.

Root: c:\worktest\SharedLib\Common
//SharedLib/maindev/delphi/subdir/GTIGDI/* //myclient/*
//SharedLib/maindev/delphi/subdir/Help/* //myclient/*


This works for the first line, but the second will be ignored. Any suggestions?

-------------------------------------------------------
Cynthia Libby
cynthia_libby <at> intuit.com
Senior Software QA Engineer
5601 Headquarters Drive
Plano, TX75024-2262

214-387-2573
x72573

 

_______________________________________________
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
Russell C. Jackson | 1 Feb 01:45 2005

RE: [p4] Client spec help needed

You can force the second line by adding + in front of it. It isn't the ideal way to setup a client, but it will work if it is necessary for your setup.
 
Rusty
 
 

From: perforce-user-bounces <at> perforce.com [mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Libby, Cynthia
Sent: Monday, January 31, 2005 1:04 PM
To: 'perforce-user <at> perforce.com'
Subject: [p4] Client spec help needed

We have a directory in perforce with multiple subdirectories. We want to map two of those directories into one directory and ignore the others. Since the client spec lines build upon each other I can't figure out how to do this.

Root: c:\worktest\SharedLib\Common
//SharedLib/maindev/delphi/subdir/GTIGDI/* //myclient/*
//SharedLib/maindev/delphi/subdir/Help/* //myclient/*

This works for the first line, but the second will be ignored. Any suggestions?

-------------------------------------------------------
Cynthia Libby
cynthia_libby <at> intuit.com
Senior Software QA Engineer
5601 Headquarters Drive
Plano, TX 75024-2262
214-387-2573
x72573


_______________________________________________
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
Smith, Jeremy R (CACI | 1 Feb 01:58 2005

RE: [p4] Continuous integration tools

I went with recurring cron jobs. :)  Most of what CruiseControl and
Anthill does is recurring ant tasks.  You can use triggers as well,
which is the paradigm I like better.

Maven is a more advanced problem, but it assumes a little bit more about
your project than what's accurate for ours.  

Jer

-----Original Message-----
From: perforce-user-bounces <at> perforce.com
[mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Jim Crossley
Sent: Monday, January 31, 2005 9:13 AM
To: Ken.Williams <at> thomson.com; perforce-user <at> perforce.com
Subject: RE: [p4] Continuous integration tools

Both of them integrate very well with Perforce.  Personally, I would be
far less happy with "a couple of recurring cron jobs."

-----Original Message-----
From: perforce-user-bounces <at> perforce.com on behalf of
Ken.Williams <at> thomson.com
Sent: Mon 1/31/2005 10:51 AM
To: perforce-user <at> perforce.com
Subject: [p4] Continuous integration tools

Hi all,

I'm getting some requests from developers in our group to investigate
Continuous Integration tools like Ant Hill and Cruise Control.  From my
first impressions, it looks like they're both oriented toward CVS
development (dealing with lack of atomic commits, lack of monotonic
changelist numbers, etc.) and we might be happier with just a couple
recurring cron jobs.

Anyone have experience or insight here?

 -Ken

_______________________________________________
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

_______________________________________________
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

_______________________________________________
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

Douglas Palmer | 1 Feb 02:42 2005

Re: [p4] Reverting unchanged resolved files


Ed,
If you revert those files, the new branch relationship will not be established. A re-branch is one of those times where it is OK to check in "unchanged" files, as it is the only way to update the metadata.
If the existing metadata has the correct branch relationship then you should be safe to revert, but even then I'd prefer to have a complete changelist that can be referred to as the new birthday of the branch.
---------------------------------
Doug Palmer
Accelrys
10188 Telesis Court
San Diego, CA 92121
www.accelrys.com
858.799.5563

perforce-user-bounces <at> perforce.com wrote on 01/31/2005 12:56:34 PM:

> I am using "p4 integ -f -b <branchspec>", followed by "p4 resolve -
> at", to re-branch one of our feature branches.  At this point, I
> would like to "p4 revert -a" to revert files that had not previously
> changed on the branch, but "revert -a" does not act on these files.
> Using "p4 diff -sr | p4 revert" doesn't work because the differences
> due to the expanded "$Id" keyword are reported.
> Short of writing a Perl script to do "p4 diff" each opened file, and
> stripping out diffs due to the "$Id" keyword, is there an easy way
> to revert unchanged, resolved files?
> Thanks,
> Ed
> Ed Mack
> Configuration Developer
> WRQ, Inc.
> 206.217.7469
> edm <at> wrq.com
> WRQ software extends host applications, rapidly integrating them for
> new applications or new users.
> Rated #1 in customer support. Relied on daily by four out of five
> Fortune 500 companies. _______________________________________________
> 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
_______________________________________________
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
rajulvora | 1 Feb 02:55 2005
Picon

Re: [p4] Reverting unchanged resolved files

have your tried doing 'p4 resolve -as' instead of 'p4 resolve -at'?
>From your description (rebranch), I believe the -as is the minimalist
safe operation you want. 'p4 revert -a' should then revert the ones
without "pending integration records" (from p4 help revert).

Rajul

On Mon, 31 Jan 2005 12:56:34 -0800, Ed Mack <edm <at> wrq.com> wrote:
>  
> 
> I am using "p4 integ -f -b <branchspec>", followed by "p4 resolve -at", to
> re-branch one of our feature branches.  At this point, I would like to "p4
> revert -a" to revert files that had not previously changed on the branch,
> but "revert -a" does not act on these files. 
> 
> Using "p4 diff -sr | p4 revert" doesn't work because the differences due to
> the expanded "$Id" keyword are reported. 
> 
> Short of writing a Perl script to do "p4 diff" each opened file, and
> stripping out diffs due to the "$Id" keyword, is there an easy way to revert
> unchanged, resolved files? 
> 
> Thanks, 
> Ed 
> 
> Ed Mack
>  Configuration Developer
>  WRQ, Inc.
>  206.217.7469
>  edm <at> wrq.com 
> 
> WRQ software extends host applications, rapidly integrating them for new
> applications or new users.
>  Rated #1 in customer support. Relied on daily by four out of five Fortune
> 500 companies. 
> _______________________________________________
> 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
> 
> 
> 

--

-- 
Rajul Vora
Please note new email address rajulvora <at> gmail.com
rajulvora <at> yahoo.com is now forwarded to rajulvora <at> gmail.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

Ed Mack | 1 Feb 03:05 2005

RE: [p4] Reverting unchanged resolved files

I'm not really after "safe", because I definitely want changes from the
source branch to override the target of the merge.  What I'd like to
avoid is an unnecessary submit of files that never changed on the target
branch.

Thanks,
Ed

-----Original Message-----
From: rajulvora <at> gmail.com [mailto:rajulvora <at> gmail.com] 
Sent: Monday, January 31, 2005 5:56 PM
To: Ed Mack
Cc: perforce-user <at> perforce.com
Subject: Re: [p4] Reverting unchanged resolved files

have your tried doing 'p4 resolve -as' instead of 'p4 resolve -at'?
>From your description (rebranch), I believe the -as is the minimalist
safe operation you want. 'p4 revert -a' should then revert the ones
without "pending integration records" (from p4 help revert).

Rajul

On Mon, 31 Jan 2005 12:56:34 -0800, Ed Mack <edm <at> wrq.com> wrote:
>  
> 
> I am using "p4 integ -f -b <branchspec>", followed by "p4 resolve
-at", to
> re-branch one of our feature branches.  At this point, I would like to
"p4
> revert -a" to revert files that had not previously changed on the
branch,
> but "revert -a" does not act on these files. 
> 
> Using "p4 diff -sr | p4 revert" doesn't work because the differences
due to
> the expanded "$Id" keyword are reported. 
> 
> Short of writing a Perl script to do "p4 diff" each opened file, and
> stripping out diffs due to the "$Id" keyword, is there an easy way to
revert
> unchanged, resolved files? 
> 
> Thanks, 
> Ed 
> 
> Ed Mack
>  Configuration Developer
>  WRQ, Inc.
>  206.217.7469
>  edm <at> wrq.com 
> 
> WRQ software extends host applications, rapidly integrating them for
new
> applications or new users.
>  Rated #1 in customer support. Relied on daily by four out of five
Fortune
> 500 companies. 
> _______________________________________________
> 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
> 
> 
> 

--

-- 
Rajul Vora
Please note new email address rajulvora <at> gmail.com
rajulvora <at> yahoo.com is now forwarded to rajulvora <at> gmail.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

Ed Mack | 1 Feb 03:14 2005

RE: [p4] Reverting unchanged resolved files

Doug,
The branch relationship was established the first time--the integration history, anyway.  I understand what you're saying, and I can live with the extra metadata--if I have to, but I would rather avoid the extra revisions.  In this case, I would be submitting over 14,000 files when it would be necessary to only submit a few hundred, at most.
 
I see the usefulness in having a diff command option that would ignore differences due to keywords.  The Thompson Toolkit diff implemented this extension for RCS keywords.
 
Thanks for the suggestion,
Ed

From: Douglas Palmer [mailto:dpalmer <at> accelrys.com]
Sent: Monday, January 31, 2005 5:43 PM
To: Ed Mack
Cc: perforce-user <at> perforce.com; perforce-user-bounces <at> perforce.com
Subject: Re: [p4] Reverting unchanged resolved files


Ed,
If you revert those files, the new branch relationship will not be established. A re-branch is one of those times where it is OK to check in "unchanged" files, as it is the only way to update the metadata.
If the existing metadata has the correct branch relationship then you should be safe to revert, but even then I'd prefer to have a complete changelist that can be referred to as the new birthday of the branch.
---------------------------------
Doug Palmer
Accelrys
10188 Telesis Court
San Diego, CA 92121
www.accelrys.com
858.799.5563

perforce-user-bounces <at> perforce.com wrote on 01/31/2005 12:56:34 PM:

> I am using "p4 integ -f -b <branchspec>", followed by "p4 resolve -
> at", to re-branch one of our feature branches.  At this point, I
> would like to "p4 revert -a" to revert files that had not previously
> changed on the branch, but "revert -a" does not act on these files.
> Using "p4 diff -sr | p4 revert" doesn't work because the differences
> due to the expanded "$Id" keyword are reported.
> Short of writing a Perl script to do "p4 diff" each opened file, and
> stripping out diffs due to the "$Id" keyword, is there an easy way
> to revert unchanged, resolved files?
> Thanks,
> Ed
> Ed Mack
> Configuration Developer
> WRQ, Inc.
> 206.217.7469
> edm <at> wrq.com
> WRQ software extends host applications, rapidly integrating them for
> new applications or new users.
> Rated #1 in customer support. Relied on daily by four out of five
> Fortune 500 companies. _______________________________________________
> 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
_______________________________________________
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
steve | 1 Feb 06:48 2005

[p4] Re: Journal file warning

Robert is correct.  The fact that they were created at the same time 
supports that, not contradicts it.  The journal that was active at the time 
you took the checkpoint represents everything that happened since 
checkpoint.213.  The checkpoint is a snapshot of the whole picture when you 
take it.  Therefore, checkpoint.213 is a snapshot of last time, journal.213 
is an archive of what has happened since last time, and checkpoint.214 is a 
snapshot of everthing this time.  That's the way Perforce and journalling 
systems in general work. 

Steve 

Serdar Kilic  IMA writes: 

> My numbering sequence is not the same as Robert noted, ours is: 
> 
> 31/01/2005  11:45p           1,957,904 checkpoint.214
> 31/01/2005  11:45p                 257 journal.213 
> 
> P4 Verify doesn't report any errors, so if we continue using this n - 1
> method I'm assuming all should still be OK, right? 
> 
> Regards,
> Serdar Kilic 
> 
> --
> <p>(02) 9828 9849
>  
> -----Original Message-----
> From: perforce-user-bounces <at> perforce.com
> [mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Robert Cowham
> Sent: Monday, 31 January 2005 10:15 PM
> To: 'tom sd fd'; perforce-user <at> perforce.com
> Subject: RE: [p4] Journal file warning  
> 
> The reason for the numbering sequence is:
>  
> checkpoint N = checkpoint N-1 + journal N-1
>  
> Thus checkpoint.24 = checkpoint.23 + journal.23
>  
> This is the reason for the error message - journal.23 is "old stuff" and
> already included in checkpoint.24. If checkpoint.24 is your latest
> checkpoint, then do you have a journal (the live journal - log of
> changes since checkpoint.24) available?
>  
> If so, then you could include it in the restore. 
>  
>     move all the db.* files to somewhere else (for safety)
>     p4d -r <path> -jr checkpoint.24 journal
>  
> If not, then what you have just done is fine.
>  
> Robert 
> 
> **********************************************************************
> This communication should be read only by those persons to whom it is addressed and its content is not
intended for use by
> any other persons.  If you have received this message in error,
> please notify us immediately by return email.  Please also destroy
> and delete the message and any attachments from your computer.
> Any unauthorised form of reproduction of this message or any
> of its attachments is strictly prohibited.
> This communication may be a personal message and may not
> represent the views of Inchcape.  Inchcape is not liable for the
> proper and complete transmission of the information contained in
> this communication, nor for any delay in its receipt.
> [mailto:admin <at> inchcape.com.au]
> ********************************************************************** 
> 
> _______________________________________________
> 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

====================
Stephen Vance
http://www.vance.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

Robert Cowham | 1 Feb 10:33 2005
Picon

RE: [p4] Reverting unchanged resolved files

As Doug says you may need to do the branch of unchanged files in this
instance for relationship purposes.

What can work quite well in such situations is to divide up the submit into
2 changelists - one for files that have "really changed", and the other for
the ones that are just for the relationship.

Without keyword expansion, the second is:

P4 diff -sr | p4 reopen -c 1234

Where 1234 is a new pending changelist.

With keyword expansion you are currently reduced to scripting. It would be
nice if Perforce could add an extra flag for this sort of situation. Why
don't you suggest this to support?

Robert

> -----Original Message-----
> From: perforce-user-bounces <at> perforce.com 
> [mailto:perforce-user-bounces <at> perforce.com] On Behalf Of 
> Douglas Palmer
> Sent: 01 February 2005 01:43
> To: Ed Mack
> Cc: perforce-user-bounces <at> perforce.com; perforce-user <at> perforce.com
> Subject: Re: [p4] Reverting unchanged resolved files
> 
> 
> Ed,
> If you revert those files, the new branch relationship will 
> not be established. A re-branch is one of those times where 
> it is OK to check in "unchanged" files, as it is the only way 
> to update the metadata. 
> If the existing metadata has the correct branch relationship 
> then you should be safe to revert, but even then I'd prefer 
> to have a complete changelist that can be referred to as the 
> new birthday of the branch. 
> ---------------------------------
> Doug Palmer
> Accelrys
> 10188 Telesis Court
> San Diego, CA 92121
> www.accelrys.com
> 858.799.5563 
> 
> perforce-user-bounces <at> perforce.com wrote on 01/31/2005 12:56:34 PM:
> 
> > I am using "p4 integ -f -b <branchspec>", followed by "p4 resolve - 
> > at", to re-branch one of our feature branches.  At this 
> point, I would 
> > like to "p4 revert -a" to revert files that had not 
> previously changed 
> > on the branch, but "revert -a" does not act on these files.
> > Using "p4 diff -sr | p4 revert" doesn't work because the 
> differences 
> > due to the expanded "$Id" keyword are reported.
> > Short of writing a Perl script to do "p4 diff" each opened 
> file, and 
> > stripping out diffs due to the "$Id" keyword, is there an 
> easy way to 
> > revert unchanged, resolved files?
> > Thanks,
> > Ed
> > Ed Mack
> > Configuration Developer
> > WRQ, Inc.
> > 206.217.7469
> > edm <at> wrq.com
> > WRQ software extends host applications, rapidly integrating 
> them for 
> > new applications or new users.
> > Rated #1 in customer support. Relied on daily by four out of five 
> > Fortune 500 companies. 

_______________________________________________
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

Robert Cowham | 1 Feb 10:49 2005
Picon

RE: [p4] Reverting unchanged resolved files

Apologies for my previous post - was jumping the gun and hadn't read the whole thread!
 
Another thought - in situations where I am rebranching using the -f flag, I usually try hard just to rebranch what is absolutely necessary and I aim to avoid doing the whole tree. Thus I would be looking to find the appropriate range of revisions that really needed to be rebranched and just do them. Sometimes this is difficult, but it's often quite easy.
 
However, I have perhaps an easier answer to your question - p4 diff2 will take account of keywords expansion properly. Thus you could use diff2 (with the branch spec) before the rebranch to find files that are the same, use some fairly simple command line piping to extract the result and save to a file for later use in your revert.
 
Robert

From: perforce-user-bounces <at> perforce.com [mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Ed Mack
Sent: 01 February 2005 02:15
To: Douglas Palmer
Cc: perforce-user <at> perforce.com
Subject: RE: [p4] Reverting unchanged resolved files

Doug,
The branch relationship was established the first time--the integration history, anyway.  I understand what you're saying, and I can live with the extra metadata--if I have to, but I would rather avoid the extra revisions.  In this case, I would be submitting over 14,000 files when it would be necessary to only submit a few hundred, at most.
 
I see the usefulness in having a diff command option that would ignore differences due to keywords.  The Thompson Toolkit diff implemented this extension for RCS keywords.
 
Thanks for the suggestion,
Ed

From: Douglas Palmer [mailto:dpalmer <at> accelrys.com]
Sent: Monday, January 31, 2005 5:43 PM
To: Ed Mack
Cc: perforce-user <at> perforce.com; perforce-user-bounces <at> perforce.com
Subject: Re: [p4] Reverting unchanged resolved files


Ed,
If you revert those files, the new branch relationship will not be established. A re-branch is one of those times where it is OK to check in "unchanged" files, as it is the only way to update the metadata.
If the existing metadata has the correct branch relationship then you should be safe to revert, but even then I'd prefer to have a complete changelist that can be referred to as the new birthday of the branch.
---------------------------------
Doug Palmer
Accelrys
10188 Telesis Court
San Diego, CA 92121
www.accelrys.com
858.799.5563

perforce-user-bounces <at> perforce.com wrote on 01/31/2005 12:56:34 PM:

> I am using "p4 integ -f -b <branchspec>", followed by "p4 resolve -
> at", to re-branch one of our feature branches.  At this point, I
> would like to "p4 revert -a" to revert files that had not previously
> changed on the branch, but "revert -a" does not act on these files.
> Using "p4 diff -sr | p4 revert" doesn't work because the differences
> due to the expanded "$Id" keyword are reported.
> Short of writing a Perl script to do "p4 diff" each opened file, and
> stripping out diffs due to the "$Id" keyword, is there an easy way
> to revert unchanged, resolved files?
> Thanks,
> Ed
> Ed Mack
> Configuration Developer
> WRQ, Inc.
> 206.217.7469
> edm <at> wrq.com
> WRQ software extends host applications, rapidly integrating them for
> new applications or new users.
> Rated #1 in customer support. Relied on daily by four out of five
> Fortune 500 companies. _______________________________________________
> 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
_______________________________________________
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

Gmane