Preserving CVS $Header$ keyword while converting to Mercurial

Kevin O. Grover kevin at kevingrover.net
Sat Jan 12 16:21:31 UTC 2013


Header's are NOT part of normal DVCS systems.   Hg has an extension
(keyword, http://mercurial.selenic.com/wiki/KeywordExtension).   Read about
and enable it, and it will expand keywords.


On Sat, Jan 12, 2013 at 7:46 AM, Jan Vrany <jan.vrany at fit.cvut.cz> wrote:

> > Jan Vrany wrote, On 01/12/2013 02:28 PM:
>
>> Hi,
>>>
>>> I would like to switch from CVS/SVN combination to Mercurial.
>>> For some time, possibly quite long, there will be a living CVS
>>> repository (not all individuals/companies are wiling to switch now
>>> to an unknown/unproven technology while the current one
>>> "just works" :-)
>>>
>>> The idea is to keep default branch intact and regularly fetch changes
>>> from CVS by running hg convert and do all development in a different
>>> branch(es).
>>>
>>> To be able to track changes, I would need to preserve expanded
>>> $Header$ keywords in files so I new from which CVS revision the file
>>> is derived. Is that possible with hg convert? If not, what would be
>>> the best approach to do it? I don't mind a bit of python coding.
>>>
>>
>> That is not something 'hg convert' cares about, so I guess it just get
>> passed through as you want. Give it a try.
>>
>>
> It does not. It leaves $Header$ unexpanded. See bottom of
>
> https://swing.fit.cvut.cz/hg/**stx.libbasic/file/**bb6ff651e27e/**
> ProjectDefinition.st<https://swing.fit.cvut.cz/hg/stx.libbasic/file/bb6ff651e27e/ProjectDefinition.st>
>
> Jan
>
>
>
>
>
> ______________________________**_________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/**listinfo/mercurial<http://selenic.com/mailman/listinfo/mercurial>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20130112/f23d7e94/attachment-0002.html>


More information about the Mercurial mailing list