Re: The cvs2svn:cvs-rev property
| From: | Simion Onea | Date: | Wed, 08 Jul 2015 05:52:01 +0000 |
| Subject: | Re: The cvs2svn:cvs-rev property | ||
| References: | 1 2 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969385801@lists.php.net to get a copy of this message | ||
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.