Re: The cvs2svn:cvs-rev property

The only SVN keywords we use is Revision, so if that is missing then yes its worth doing a sweeping commit. Making all keywords consistent across all files is not, as we don't use any other keywords anyway. As for eol-style, it has been a while since I remember it being a problem. It doesn't change anything in the docs themselves, and I haven't heard anyone complaining that their editor was incapable of displaying correct new lines... I'm sure there are other things to do -- but hey, if you are bored and it won't conflict with other peoples work.. sure. Fix the eol-style -- but if that requires actually changing any files content -- then remember the whitespace rant: http://doc.php.net/tutorial/whitespace.php -Hannes On Tue, Jul 7, 2015 at 10:52 PM, Simion Onea <simionea@gmail.com> wrote: > On Tue, Jul 7, 2015 at 6:46 PM, Hannes Magnusson > <hannes.magnusson@gmail.com> wrote: >> >> On Tue, Jul 7, 2015 at 7:36 AM, Simion Onea <simionea@gmail.com> wrote: >> > Hello! >> > >> > Do we need the "cvs2svn:cvs-rev" SVN property on the files any more? >> >> >> >> Considering the last remaining cvs backup isn't public, no we don't. >> But there is also no gain whatsoever in removing it. >> >> When we move to another version control system, maybe the conversion >> process can pickup on the attribute an annotate the object. >> Say, you could see the transition from cvs->svn->git and graph it out >> over time. Which version control was most active. Which caused most >> followups. Blablabla. >> >> Please don't remove it. >> >> -Hannes > > > Thanks for the answer, Hannes! > > The reason I asked is because I noticed that many files in the "en" tree and > also in the translations do not have the correct values for the necessary > attributes -- "svn:eol-style" and "svn:keywords". Sometimes these > attributes > are missing. And I thought about correcting these issues. > I understand the implications of making changes in many files of the "en" > tree. I learned my lesson last time I did it :-) > The translated files which are up-to-date must be updated after changing the > "en" file. > > What do you think? Is it worth doing such a clean-up? > > Regards, > Simion.