44 messages in com.perforce.perforce-user[p4] Peforce History in source code
FromSent OnAttachments
Joe Cotellese14 Oct 1999 09:58 
Alex Nicolaou14 Oct 1999 14:24 
Kevin L. McWhirter14 Oct 1999 21:05 
Michael Peppler15 Oct 1999 06:55 
Mike Meyer15 Oct 1999 08:21 
Gregg G. Wonderly15 Oct 1999 08:40 
Dave Foglesong15 Oct 1999 08:58 
Paul Jackson15 Oct 1999 10:08 
Greg Spencer15 Oct 1999 10:17 
Kevin L. McWhirter18 Oct 1999 18:52 
Kevin L. McWhirter18 Oct 1999 18:57 
Paul Jackson18 Oct 1999 19:50 
Kevin L. McWhirter18 Oct 1999 20:19 
Marc Kwiatkowski18 Oct 1999 22:25 
Hoff, Todd19 Oct 1999 07:10 
David Weller19 Oct 1999 07:22 
Rob Juergens19 Oct 1999 07:26 
Roger Day19 Oct 1999 07:27 
Michael Peppler19 Oct 1999 07:34 
Paul Jackson19 Oct 1999 07:42 
Short, Todd19 Oct 1999 07:53 
Ken Rice19 Oct 1999 07:56 
Dave Lewis19 Oct 1999 08:07 
Sam Falkner19 Oct 1999 09:04 
Paul Goffin19 Oct 1999 09:12 
Ines Heinz19 Oct 1999 09:32 
Richard Brooksby19 Oct 1999 09:45 
Rick Macdonald19 Oct 1999 11:16 
Rajul Vora19 Oct 1999 17:35 
Paul Jackson19 Oct 1999 20:56 
Anthony Kolarik20 Oct 1999 06:14 
Michael Go20 Oct 1999 08:14.bin
Christian Ludloff20 Oct 1999 09:43 
Scott Blachowicz20 Oct 1999 10:10 
Marc Kwiatkowski20 Oct 1999 10:17 
Michael Go20 Oct 1999 11:00.bin
Joe Cotellese20 Oct 1999 14:32 
Dave Lewis20 Oct 1999 14:52 
Mike Meyer20 Oct 1999 15:06 
Joan Yuen20 Oct 1999 15:16 
Piaw Na20 Oct 1999 15:57 
Andrew Dalgleish20 Oct 1999 17:38 
David Corbin21 Oct 1999 11:27 
Mike Meyer21 Oct 1999 13:20 
Subject:[p4] Peforce History in source code
From:Mike Meyer (mw@phone.net)
Date:10/20/1999 03:06:31 PM
List:com.perforce.perforce-user

Joe Cotellese writes: ;->It seems that when you branch and try to view the history of the branched
file, ;->it doesn't show you the history prior to the branch, I understand why and it ;->makes sense however there are cases where I need this information. Putting
it ;->into $Log made the most sense to me.

Um - actually, $Log$ (if they ever do it, gods forbid) should track filelog.

What you really want is more information from filelog. Unfortunately, that isn't trivial, because you then have multiple history lists feeding the file.

;->There probably is a way to do this via scripting and the command-line but a
lot ;->of my users are Windows GUI guys that don't do the command-line (at least not ;->without a lot of wailing and teeth gnashing).

What I do for people like that is put cgi scripts on a web server running on the perforce server. It works fairly well.

In this case, it may be ideal. Some of the fancier web-based depot browsers can do integrated file histories - they may provide what you are looking for.

<mike