[p4] Peforce History in source code

Rob Juergens robj at vsi.com
Tue Oct 19 07:26:45 PDT 1999


The other problem is that having "change comments" in the source file
messes up diffs to find out what has changed.

I vote for leaving it out and using separate cmds to access changes info.


-----Original Message-----
From: David Weller [mailto:David.Weller at riva.com]
Sent: Tuesday, October 19, 1999 7:23 AM
To: Hoff, Todd; perforce-user at perforce.com
Subject: RE: [p4] Peforce History in source code


I agree with this point also.  However, we "solved" the $Log vs. ~$Log
argument by having the $Log data placed at the _bottom_ of the file (old
SCCS days).

Maybe Perforce can do this?

> On the same theory i vote against also. There's nothing
> worse than seeing 10K of mostly useless comments at the
> beginning of a file, especially when they are easily
> retrievable with a tool. Also, meta-data and data are better
> left separate.
>


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




More information about the perforce-user mailing list