Seems Ok for me.
This change imply a lot of modifications into the editor in several places.
I will be able to work on this in one or 2 weeks.
Best,
Yannick
2011/9/3 Александр Москалёв
> I think we must create global "new" directories and save new files in it.
>
> data/phpdoc-all/
> data/phpdo
I think we must create global "new" directories and save new files in it.
data/phpdoc-all/
data/phpdoc-all.new/
data/peardoc/
data/peardoc.new/
phd/
revchek/
In this case we no need ".new" postfix in file name and this
directories will be not under version control.
With regards, Alexander Moska
Great catch Irker !
For the possible solution, I don't thinks it's a good way to force svn
update to this folders/files.
We must thinks about anothers solutions to fix this issues, specialy for new
folder as you explain.
Now we understand what's append, we can fix it manually before a "good"
solu
Becouse --force not going to external we must replace "svn up" by "svn
up --force en/ ru/ pt/ es/"(and other lang) .
Today I update manually (svn up --force ru/& run cron script) RU
directory and response good result.
I will try to make commit tomorrow.
And new question:
In some languages
I found what option '--force' for svn update can temporary solve this bug.
If no one is against, I might add this option? Maybe there are some
bad features, which I do not know?
With regards, Alexander Moskaliov
ir...@irker.net
2011/9/2 Александр Москалёв :
> Let me explain with an example:
> 1)
Let me explain with an example:
1) Site User translate new file
language/predefined/errorexception/etseverity.xml.new and save it
2) Site ceate language/predefined/errorexception directory and
etseverity.xml.new fileNOT under version control
3) User with SVN account created same directory or on
You say that it's .new files who make some problem with svn ? right ?
Please, give us all information that you have found, I will try to take a
look quickly.
Best,
Yannick
2011/9/2 Александр Москалёв
> I think I found a bug. Problem with svn conflict.
> The site provides a directory that does
I think I found a bug. Problem with svn conflict.
The site provides a directory that does not add a version control and
causes conflicts.
Because of these conflicts in several languages files are not updating.
And this is a critical issue.
We can get rid of the force of these conflicts, but I thi
Hannes is true ! One hour and the code base is updated.
About this desync :
Generally, this is a bug. We must fix all svn problem from the repository
used by the editor and try to find out where is the primary problem.
If you want to try to catch some :
1) Sync the online editor and your copy.
Sorry, wrote wrong table. This is actual:
RU files | edit.php.net | edit.irker.net
uptodate | 1495 | 1581
old | 112 | 86
not translate| 8261 | 8501
total |
On Fri, Sep 2, 2011 at 09:52, Александр Москалёв wrote:
> And i already commited small fix. You manualy updating site or it's
> updates automaticaly?
The code base updates every hour I believe.
Migrations and those sort of things are done manually.
-Hannes
Hi!
I try optimise or fix update script becouse we have BIG desync between
edit.php.net and repository.
Desync kept also after you run update script.
For example, I have my local copy of doc-editor with actual file states:
RU files | edit.php.net | edit.irker.net
--
2011/8/31 Александр Москалёв
> Hello!
>
Hi Irker ;)
>
> Yannick, this mail is primarily for you, but I decided that I can
> discuss it with everyone.
>
> As I already told you, I will try to join the development edit.php.net.
>
> The first thing I want to optimize the updating cron script.
> N
Hello!
Yannick, this mail is primarily for you, but I decided that I can
discuss it with everyone.
As I already told you, I will try to join the development edit.php.net.
The first thing I want to optimize the updating cron script.
Now when you run it removes all data from the database and all f
14 matches
Mail list logo
