There is more information (and other good reasons) if you look through
the mailing list archive, but:
1. Comments are available directly from the repository when needed
2. A prepended or appended log is guaranteed to cause merge conflicts
(at least with diff/patch)
3. find and replace and other user local edits make these comments get
out of sync.
4. it is possible to append these types of history logs via an external
script for the users who still need this functionality.
-David Waite
On Jun 13, 2004, at 5:00 AM, Benjamin Zeiss wrote:
> hi,
>
> --On Sunday, June 13, 2004 10:27:16 AM +0200 Erik Huelsmann
> <e.huelsmann@gmx.net> wrote:
>
>>> Is it possible to add the commit comment to the file itself.
>>> I mean, suppose I have a CPP file, can I add my comment to this file
>>> automagically,
>>
>> This has deliberately not been implemented. What you describe is the
>> behaviour of the CVS $Log$ keyword. This keyword is known to cause
>> lots of
>> problems with branching and merging.
>
> i would be interested in a more technical explanation why this causes
> trouble. i too miss such a feature...
>
> --
> Benjamin Zeiss
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jun 13 19:26:44 2004