[crossfire] CVS -> SVN conversion

[Tchize]

Mark Wedel a écrit :
>>> 4) I don't believe the SVN by default provides support for the $Id$ string 
>>> version control at the top of files.  I thik there may be modules that support 
>>> it, but sourceforge is very particular in what modules they support (short list 
>>> being ones that provide e-mail notification, and another that checkes file names 
>>> for reasonable compliance).  There may be client side scripts that could be 
>>> used, but then that seems a little more problematic (some developers forget to 
>>> use/install them, so their commits are not updated, etc).  Does it just make 
>>> sense to pull the $Id strings out of the files then?
>>>   
>>>       
>> Well, the $Id strings have never seemed terribly useful to me (it was
>> often more convenient for me to just check the timestamp of the build
>> and/or source directory if I wanted to know when in CVS it was built
>> from), however if anyone has any use for them, probably wouldn't be
>> difficult to make a script to generate a .h file containing macros of
>> that data, and put that in as part of the build system.
>>     
>
>   The client had been modified at one point to provide that information, just to 
> be more helpful in bug reports.
>
>   That said, I agree that the header in each file probably isn't necessary.  It 
> might be nice to include the svn commit number in a header file, so that could 
> be displayed, eg, the client could say something like:
>
>   Crossfire Client 1.10 build 8963
>
>   Such that if a user reports a bug, we can easily check that global revision 
> number and see if the bug may have been fixed, etc.
>
>   
Yes client has been modified in past to provide id of different modules.
However those were made because CVS had no notion of global version
numbers and it was the most easy way to find out which cvs version the
user was using when reporting bug. Using the global svn revision number
+ branch can replace this
Crossfire gtk client 2.1.0 (/branches/XYZW/client revision 1234)
Branch name is important to include in bug report as well as revision
number :-)