[cvsnt] $Log$ conflict

[Ian Epperson]

> -----Original Message-----
> From: Tony Hoyle [mailto:tmh at nodomain.org] 
> Sent: Monday, August 18, 2003 4:58 AM
> To: cvsnt at cvsnt.org
> Subject: Re: [cvsnt] $Log$ conflict
> 
> 
> Tom Cmok wrote:
> 
> > ..but I'm pretty sure for some earlier versions (<2 maybe) of cvsnt
> > I was not having this problem - during branch merging - yes, but
> > not for a 'normal' update. Why is there that additional new $Log$
> > line:
> > 
> $Log$ has always been a complete pig to maintain...  I've never seen a
> conflict during a normal update (in fact it's impossible to 
> get a conflict
> unless you've modified the file somehow) but then I stopped 
> using $Log$ for
> most things years ago, because it generates huge files with 
> no information
> you can't get elsewhere anyway.
> 
> Tony

It was pointed out in our shop by a guy who used to do programming for
medical devices that you REALLY don't want to put the log into your source
code.  He did that ONCE, and when the code was audited, the auditor noted
all the bug fix log entries and asked to see ALL OF THE PROBLEMS AND FIXES.
This was abnormal, but because it was in the code comments it opened the
door.  

We don't do near the kind of work here - but when we had a disgruntled
customer, they demanded a code audit.  I was VERY GLAD there was no log info
in the code as they could have grilled us over every little bug fix, instead
of the finished product.