[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion Question

From: Duncan Booth <duncan.booth_at_suttoncourtenay.org.uk>
Date: 2007-03-08 12:39:28 CET

Paul <alabamapaul@gmail.com> wrote:

> On 3/7/07, sergs_castillo@yahoo.com <sergs_castillo@yahoo.com> wrote:
>> Developer committing a fixed code:
>> $ cvs -d developer1@host commit -m "comment" <file>
>>
>> Is there a similar way to do this in SVN?
>>
>
> svn commit --no-auth-cache --username developer -m "comment" filename
>
> This will prompt the developer for their password, but the username
> and password will not be stored (--no-auth-cache)

If you have a subversion checkout on a production system (as the OP
said), then I would strongly advise making sure the subversion config
file has:

[auth]
store-auth-creds = no

otherwise you (or someone else) is bound to forget the --no-auth-cache
option someday. We use an account with read-only access to do the
initial checkout with store-auth-creds turned on, then disable it for
all further access.

There is a slight problem with this scheme if you forget to supply the
username as a command line argument. When you do a commit it will prompt
for an alternative username/password. Unforunately (at least for https:
protocol) it then fails to commit so you have to rerun the command with
the missing arguments.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 8 12:40:27 2007

This is an archived mail posted to the Subversion Users mailing list.