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

Re: Keeping tags/ and branches/ in the "trunk"

From: Andy Levy <andy.levy_at_gmail.com>
Date: Mon, 25 Jan 2010 11:18:39 -0500

On Mon, Jan 25, 2010 at 11:05, trans <transfire_at_gmail.com> wrote:
> On Jan 25, 9:30 am, Andy Levy <andy.l..._at_gmail.com> wrote:
>> I don't understand what advantage this would give you. I do see the
>> potential for a lot of confusion and copying/moving of items which
>> shouldn't be operated on, though.
>> Subversion itself applies no special meaning to "tags" & "branches" so
>> there is nothing *technical* from stopping you from doing this; it
>> seems like you're going against convention for no discernible reason
>> though.
> Merely convenience --perhaps a minor reason, but a reason nonetheless.
> At least for me, I find it nice to have the source code closer to the
> surface. Having now used git for some projects its one of the things I
> find I like about it. However I prefer Subversion's approach to tags
> and branches. So I simply wondered, would it be possible to have both?
> But there are problems with the approach, e.g. checking out the trunk
> would pull down the tags and branches as well. So I am inquiring if
> there is anyway to configure Subversion to exclude paths from a
> checkout, as well as tagging, branching, etc. that would make this
> doable.

Sparse Checkouts will handle the former, but the latter you'll have to
step very carefully or script your branching & tagging (and may have
to do it in steps, instead of all at once).
Received on 2010-01-25 17:19:14 CET

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.