Nuno Lopes wrote:
>> This is important, because usual CVS users will still do
>> translations. Also it is important for this system to handle
>> colissions. It is not at all sure that the cronjob will be able to
>> commit the changes, if one CVS user changes the file between the
>> moment someone e
OK, I'm gonna do this. I will let the admin to add new users without CVS
account. Those users will commit with a default account. Later, if they want
to continue translating, encurage them to get a CVS account.
Great. As I have said before, getting a CVS account is also a kind of
reward (you also
> I think that this system should use Joe's account (imaginary), if he has
> one, but if he has no cvs account, then it should be committed with a
> default translation group account. It is important to keep as much
> information in the CVS logs as possible, so cvs commits should reflect
> the user
I need your oppinion about the way how commits will work in the web
interface to translate the manual.
There was an idea to solve the problem of being always changing CVS dir with
the user's information.
The solution would be to have just a CVS account (that hot solution) and all
commits would be d
-Mensagem Original-
De: "Nuno Lopes" <[EMAIL PROTECTED]>
Para: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Enviada em: domingo, 19 de outubro de 2003 15:52
Assunto: [PHP-DOC] commit files with the web interface
> Hello,
>
> I need your oppinion about
Hello,
I need your oppinion about the way how commits will work in the web
interface to translate the manual.
There was an idea to solve the problem of being always changing CVS dir with
the user's information.
The solution would be to have just a CVS account (that hot solution) and all
commits
