[p4] Peforce History in source code

[Greg Spencer]

> 3. They can't believe that Perforce doesn't support a full set of keywords
> when RCS, PVCS, SourceSafe, etc., all do, and have done so years. (And if
at
> the archive file level Perforce uses RCS, then it shouldn't be too
difficult
> for them to enable this.)

It's not as easy as you might think -- Perforce doesn't store any of the log
information in the RCS files it uses -- they're just for storing the
revisions.  All the log information is stored in Perforce's database.

I think they should support it, but only as an option.  At least it would
stop a new user from asking where the $Log$ keyword is every month or two.
:-)

Personally, I'd create scripts that insert the $Log$ (or it's equivalent,
with different syntax, so it could be easily removed) entries on sync, and
remove them again on submit/diff/merge (but only for ktext files), to keep
them from polluting the database and diffs.  It's all easily possible with
the existing perforce commands.  You could also have complete control over
what info gets inserted
too.

                        -Greg.