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

Re: svn modules (was Re: Features and release dates)

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-05-02 00:26:37 CEST

Nicklas Larsson <kilsmo@lysator.liu.se> writes:

> > Let's look at how this would work:
> >
> > svn co http://foo/repo/trunk/foo/
> > cd foo
> > svn ln http://foo/repo/trunk/doctools/ .
> > svn ci
> > svn up # at this point the doctools directory becomes populated


> > This is more general-purpose and much more flexible than modules.
> > What does everyone think?
> If I do not want to use doctools main trunk version, but a bug fixed and
> stable version (tagged with DOCTOOLS_STABLE), how should I create the link
> then?

Well, in Subversion a "tag" is simply a cheap copy, so

svn ln http://foo/repo/tags/DOCTOOLS_STABLE/ .

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 2 00:27:40 2002

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

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