RE: Keyword corresponding to $log:$ in CVS

I have sworn off using $Log$ in my code as well, unless directed by the
development process for my client. Where I am forced to include $Log$, I
always make sure I suppress keyword expansion 'prior' to performing a merge
( I usually do a "cvs up -CRAPkk ..." before my "cvs up -j ...") . Reading
Chapter6 section 2 of the book indicates that this will not be required for
general keywords. The books example of $LastDateChanged$ states that diff
un-substitutes the expansion before the commit.

Because $Log expands over multiple lines, perhaps it could be provided in
svn if it was delimited in someway - but, in my opinion, it isnt worth the
effort, is too hard (what if the log message contains the $Log delimiter ?
how to stop a false positive match searching for the delimiter), and there
are _so many_ other ways to view the log history that burying yet another
copy in your code just seems lame - the code should be related to what your
doing, not telling you what work you did before.

Leif Eriksen
Developer
HPA - IT Development
+61 3 9217 5545
leif.eriksen@hpa.com.au

-----Original Message-----
From: Branko Cibej [mailto:brane@xbc.nu]
Sent: Wednesday, June 04, 2003 7:11 AM
To: kfogel@collab.net
Cc: lars.haack@gmx.de; dev@subversion.tigris.org
Subject: Re: Keyword corresponding to $log:$ in CVS

kfogel@collab.net wrote:

>"Lars Haack" <lars.haack@gmx.de> writes:
>
>
>>I have a question concerning the keyword expansion facilities of
>>subversion. I would like to know if there is a keyword corresponding
>>to $log:$ in CVS. I often use this keyword in my sourcefiles because
>>I like the idea of having the whole history of a file inside the
>>file itself besides the actual state. Then I only have to look into
>>the file and get the information I need without having to invoke the
>>version control tool at all.
>>
>>
>
>We don't support the $Log$ keyword, at least not before 1.0.
>
>(Actually, I think we had a discussion and decided not to support it
>at all, but check this mailing list's archives to make sure.)
>
>
$Log$ is a total horror the moment you start merging changes between
branches. You're practiallly guaranteed to get conflicts there, which --
because of the nature of this keyword -- simply cannot be resolved
automatically.

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
**********************************************************************
IMPORTANT
The contents of this e-mail and its attachments are confidential and intended
solely for the use of the individual or entity to whom they are
addressed.  If you received this e-mail in error, please notify
the HPA Postmaster, postmaster@hpa.com.au, then delete 
the e-mail.
This footnote also confirms that this e-mail message has been swept for
the presence of computer viruses by MimeSweeper.  Before opening or
using any attachments, check them for viruses and defects.
Our liability is limited to resupplying any affected attachments.
HPA collects personal information to provide and market our services.
For more information about use, disclosure and access see our Privacy
Policy at www.hpa.com.au
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org