On 3/7/07, sergs_castillo@yahoo.com <sergs_castillo@yahoo.com> wrote:
> Hi,
>
> I have a question on SVN.
>
> First, we are converting CVS to SVN. One of our process is that we have a
> production system where the code are checked out from CVS using a shared
> account. This shared account is not allowed to commit changes to CVS.
> However, if a bug is found and it can be fixed right away, a developer can
> fix the file in the working directory and commit it to CVS using the
> project's working directory by overriding CVSROOT, for example:
>
> Shared account checkout the files:
> $ cvs -d sharedaccount@host checkout <file>
>
> Developer committing a fixed code:
> $ cvs -d developer1@host commit -m "comment" <file>
>
> Is there a similar way to do this in SVN?
What access method are you using?
When working on a shared server like you're describing, I prefer to
explicitly pass my credentials to svn anytime I perform an operation
to eliminate any possible bad assumptions about what svn user ID
should be used.
svn <operation> <parameters> --username=USER --password=PASS
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 7 20:02:28 2007