Author Topic: How do you commit correctly?  (Read 15585 times)

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: How do you commit correctly?
« Reply #15 on: December 14, 2005, 06:28:40 pm »
i use
url="svn+ssh://tiwag@svn.berlios.de/svnroot/repos/codeblocks/trunk"

for both, TortoiseSVN and commandline-SVN  and it works great,
but PuTTY and Pageant must be running and configured properly,
otherwise you're going nuts by typing your password all the time...

takeshimiya

  • Guest
Re: How do you commit correctly?
« Reply #16 on: December 14, 2005, 06:30:06 pm »
...the only drawback will be that TortoiseSVN will prompt you for your password every time, but that is something you can live with. It will still work!

What I didn't like is TortoiseSVN asking me the password like 3 times for everything...

Why don't you add your public key to the server? This way you only type your keyphrase once per session (i.e. between reboots).

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2790
Re: How do you commit correctly?
« Reply #17 on: December 14, 2005, 09:21:24 pm »
Thanks everyone

I think I got it done. BerliOS finally accepted the following command:
Code
C:\Usr\Proj\cbBeta>svn --username {me} --password {mypswd} commit -m "KeyBind
er changes 2005/12/14 by pecan"

It didn't ask me for any passwords either. Maybe it just accepted the
situation to get rid of me....;-}
Whew! so simple, but so hard getting there.

thomas: thanks for the detailed explanation of how to automate this.
I'll start work on that.

thanks y'all
pecan
« Last Edit: December 14, 2005, 09:28:47 pm by Pecan »

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: How do you commit correctly?
« Reply #18 on: December 15, 2005, 08:36:11 am »
Thanks everyone

I think I got it done. BerliOS finally accepted the following command:
...
fine

but after studying your previous posts, i think the only thing what you've done wrong,
was to use several backslashes "\" in your pathes given to subversion.

with svn always use "/" slashes instead.