hg status, hg diff do not consider an enabled keyword extension --> leads to empty commits

[Christian Ebert]

Hi Rupert,

* rupert.thurner on Saturday, June 06, 2009 at 00:19:21 -0700
> On 5 Jun., 22:34, Christian Ebert <blacktr... at gmx.net> wrote:
>> Am I right in the assumption that you want hg see cvs-formatted
>> $Id$'s as no change to the files in question so you can easily
>> switch between "cvs" and "hg" versions of the same file?
> 
> that was the reason, yes - your head is to clear :) we use cvs or svn
> to check out from the central repository, and hg locally to branch/
> merge. a cvs update in some cases updates the hg-hash to a cvs version
> number. i could also imagine an option that hg does not update the
> keyword at all ... but i am unsure if this also leads to a status
> change for hg.

Could you test the attached simple patch which enables keyword
expansion when running "hg convert"?

I disabled this for security reasons, and am not sure what the
ramifications are, so be careful and do not use it on production
code ;-)

I did some testing with cvs, and it seemed to work; once you
update after converting you have hg hash Id's. No need for any
special hooks. Those might be needed however when you go back to
cvs, I don't know.

c
-- 
  Was heißt hier Dogma, ich bin Underdogma!
[ What the hell do you mean dogma, I am underdogma. ]
_F R E E_  _V I D E O S_  http://www.blacktrash.org/underdogma/
                          http://www.blacktrash.org/underdogma/index-en.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kw-convert.diff
Type: application/x-patch
Size: 816 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20090607/65fc885a/attachment.bin