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

Re: Some basic svn questions.

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-12-10 18:28:10 CET

On Wed, 2003-12-10 at 10:43, olczyk@interaccess.com wrote:

> 1) Is there an equivalent to CVSROOT to specify the repository without
> typing it in on each commandline.

In general, you only need to type the URL when doing an initial
checkout. For daily working-copy work, you don't need to type URLs.
Unless you branch and tag like crazy, it's not a real problem. Most
people work around the issue by setting a custom environment variable,
like

  $ export MYREPOS=http://host/path
  $ svn co $MYREPOS/project

> 2) Is there an equivalent of .cvsignore?

Yes, it's the svn:ignore directory property. Read chapter 6.

> 3) Sometimes I have questions about how to do something in a project.
> I create a small subdirectory, and make a test case for the
> feature in there. Is there a way of not having that subdirectory
> checked in?

Huh? If you don't want a subdirectory committed, then don't 'svn add'
it.

> 4) Sometimes I wind up in a circumstance where I do not have access
> to the repository. For example I might need to look stuff up to
> get something working. So I go to the nearest university library
> and work off the laptop there. Is there a way to copy the
> repository and sync the two repositories at appropriate times?

Subversion is not a distributed repository system, like bitkeeper or
arch. There is only one repository. You can back it up with 'svnadmin
hotcopy', and then rsync the backup as much as you like. But this isn't
the same as "replication" between multiple repositories.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 10 18:28:54 2003

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.