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

Re: SVN Import command

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Fri, 3 May 2013 12:21:00 -0500

On Fri, May 3, 2013 at 11:59 AM, C M <cmanalyst66_at_gmail.com> wrote:
> I don't understand why I can't simply over-write the existing file in the
> directory? On many occasions, a build may only result in one new executable.
> To have to delete/rename the entire directory seems like overkill.

Converting the initial import directory from a non-working copy to an
svn working copy is a one-time thing. There are ways to work around
it if the executables are in-use or something that makes the rename
and checkout process a problem. The point is that to get the
versioned commits, you need to do it from an existing working copy.
You can keep re-using the same working copy for all subsequent
changes. The working copy holds a hidden 'pristine' copy of the
checked-out version, so subsequent commits know what differences to
send to the repository.

> And for the most part, we only have one top level directory below which all
> the executables are stored.

You don't have to add the /trunk, /branchs, /tags layout if it doesn't
make sense for your usage. Subversion just treats them as arbitrary
names, but by convention they can be used to give 'human friendly'
names to specific revisions. Normally the point of using a version
control system is that you have access to older versions that have
been committed and the tags just give you an easier way to find them
than knowing the repository revision number.

  Les Mikesell
Received on 2013-05-03 19:21:34 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.