> From: Les Mikesell [mailto:lesmikes...@gmail.com]
>
> Not sure what you mean about with sparse and recursive checkouts or
> why you'd start with /. If there is one project in the repository
> you would normally just check out /trunk. Or with multiple projects,
> /project_name/trunk.
... see
On Thu, Nov 28, 2013 at 8:51 AM, Edward Ned Harvey (svn4)
wrote:
>
> But I prefer to do this:
> svn co --depth=immediates $URL
> svn update --set-depth infinity project/trunk
> svn update --set-depth immediates project/branches
> svn update --set-depth infinity project/branches/eharvey
>
> Because
On 27/11/2013 16:03, Pavel Lyalyakin wrote:
> Hello Ram,
>
[snip]
>
> If you want to start using Subversion server right now, then take a
> closer look at VisualSVN Server. It installs in no time and is very
> convenient to configure and manage. In fact, VisualSVN Server works
> out of the box an
On Thu, 28 Nov 2013 10:58:08 +, Les Mikesell wrote:
...
> different people were working on the separate copies. What commit
> log message would ever be appropriate if you commit to both the trunk
> and branch through an upper level directory that ties them together?
svn commit -m 'just to co
