![]() |
![]() |
Free Books / Computers / Subversion / | ![]() |
|
![]() |
||||
![]() |
![]() |
|||
![]() |
![]() |
|||
![]() |
||||
|
|
||||
![]() |
![]() |
|||
![]() |
Authenticating as a Different User |
![]() |
||
![]() |
||||
![]() |
![]() |
![]() |
||
![]() |
||||
This section is from the "Version Control with Subversion" book, by Ben Collins-Sussman, Brian W. Fitzpatrick and C. Michael Pilato. Also available from Amazon: Version Control with Subversion.
Since Subversion caches auth credentials by default (both
username and password), it conveniently remembers who you were
acting as the last time you modified you working copy. But
sometimes that's not helpful—particularly if you're
working in a shared working copy, like a system configuration
directory or a webserver document root. In this case, just
pass the --username option on the
commandline and Subversion will attempt to authenticate as
that user, prompting you for a password if necessary.
subversion, svn, revision control, backup, review, revert, merge, commit, update, branch, changes, collision
![]() |
|
|