Re: Re: Status of doc migration to Git
| From: | Hannes Magnusson | Date: | Tue, 25 Mar 2014 01:59:23 +0000 |
| Subject: | Re: Re: Status of doc migration to Git | ||
| References: | 1 2 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969384905@lists.php.net to get a copy of this message | ||
On Mon, Mar 24, 2014 at 1:55 PM, Maciej Sobaczewski <sobak@php.net> wrote:
>> - Translation statuses; we could probably insert the Git hash in place
>> of the SVN revision number, that doesn't show how out-of-date the file
>> is though. Is there some other convenient way to replace the usage of
>> EN-Revision values, with Git? How do translators use this, if at all?
>> Do you?
>
> This would require rewritting whole system. The fact that revision ID's are
Thats the question I guess.
When we move to git.. What are our options?
Maybe this requirement isn't really useful for anyone. Just some
overzealous control freak by the "system.
What incremental numbers give us is see "how many revisions" a file is
out of date.. But really? Does that really matter?
Besides, a single revision could have dramatic changes.. or just
whitespace changes. Who should the translator care about whitespace
changes in the english version?
So even if we compare git hashes and deem the translation "out of
date" because it doesn't match... really? Isn't that just mean?
I recommend reading: http://php.markmail.org/message/3t2pmgoq35h5ogep
-Hannes