Now I'm confused. Is there a translation using git already? That is a big fat fat fat no no no no no.
The PHP VCS infrastructure is about to move to git soon (https://wiki.php.net/rfc/dvcs), yes, but there will be no translation hosted out side of the PHP VCS infrastructure for any reason whatso ever. When the conversion have finished, all translations, english and doc-base will all be in the same git infrastructure. I wonder if PhDOE could start using individual git clones? Currently all patches and all work is stored up on a single shared checkout.. which brings its own bag of problems.. If a user could commit work to his "local clone on PhDOE" ( == WIP) and then "push upstream"? that would be cool I believe. Then anonymous users could also "file a merge request" so people wouldn't have to literally login to the OE and commit patches from there? -Hannes On Sun, Dec 11, 2011 at 17:29, Yannick Torrès <yannick.tor...@gmail.com> wrote: > PhDOE is based on a VCS like Cvs or Svn. > The major difficulty is that EN documentation will be steel on Svn, and > translation, on Git. > > I'm worried about this change and the consequence on the PhDOE tools... > > Is there a treahd who explain why we must do this change ? Or it's just for > fun with Git > > I really need to understand this change. Svn just works fine according to me > to handle the documentation. > > Regards, > Yannick > > > 2011/12/11 Александр Москалёв <ir...@irker.net> >> >> 2011/12/11 Ferenc Kovacs <tyr...@gmail.com> >>> >>> http://linux.die.net/man/1/git-commit >>> >>> see --author >> >> >> From https://wiki.php.net/rfc/dvcs : >>> >>> Git can use HTTP Basic auth to verify whether a user is allowed to login. >>> We can use HTTP Digest for authentication and an update hook to check >>> whether the user is authorized to push to that directory. >> >> It will work with http basic auth? >> >> With regards, Alexander Moskaliov >> ir...@irker.net > >
