Menu
I seem to get into an annual debate about the use of the $Log$ keyword. My point of view is this:
$Log$ is white hot death.
All it does is jam marginally relevant spam into your source files. Any information that anyone thinks they might be able to get from a $Log$ is more readily available from (and is likely to be more accurate in) your version control system.
So, here's the question: how would you explain to an "old school" coder (who thinks that $Log$ is the way to manage source code changes) that we have better tools now?
The CVSNT remarks on $Log$ are a good start but they're just not pointed enough. To date, the closest that I've come to a one-liner that I've managed to come up with is "$Log$ is a wish. You're hoping that what gets spammed into your file has any relation to what really happened to this file."
PS for clarity: when I say "old school," I mean old in attitude, not old in years. My first programming paycheck (and a remarkably modest one it was, too) was sometime in 1986 and I never thought $Log$ was a good idea.
522
A risk register, sometimes known as a risk log, is an important component of the overall risk management framework. Created during the early stages of a project, the risk register is a tool that helps you track issues and address them as they arise.
Here are few points to consider to secure it: Redact/mask/anonymize sensitive information from event logs beforehand, to prevent sensitive information from being logged in plain text (e.g., PHI/PII information) Enforce role-based access controls. Perform log integrity checks to ensure that logs are not tampered with.
One of the biggest problems here is scaling. Many log management solutions will charge you a flat rate which can vary wildly instead of charging based on how much data you process and store. The difference between ten and fifty users (or ten and fifty gigabytes) is staggering.
DNS. One of the most critical network log sources is DNS. DNS logs will reveal name resolution that occurs in the environment, and depending upon the logging, who made that resolution.
I think the Subversion FAQ also has a good explanation.
$Log$ is a total horror the moment you start merging changes between branches. You're practically guaranteed to get conflicts there, which -- because of the nature of this keyword -- simply cannot be resolved automatically.
174
In addition to what the others have said, try putting a comment (/* ... */) into a commit message :->.
40
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
