we have the same problem in our shop. and we (the developer) end up committing those changes for the designer. what i'm planning to have is a small cgi script that has a textbox for commit message and a button. that script should commit the latest changes of the whole tree. (or modify some svn web frontend to interact with the working copy... hmmmm).
teaching the designer to use that interface would be much easier than teaching her to use ssh
i've tried tortoise svn, but the problem is that the designer need to work with a running version and the webapp runs on linux.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.