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

Re: UNS: Re: Subversion Doesn't Have Branches aka Crossing the Streams aka Branches as First Class Objects?

From: Thorsten Schöning <tschoening_at_am-soft.de>
Date: Sat, 18 May 2013 19:33:10 +0200

Guten Tag Zé,
am Samstag, 18. Mai 2013 um 18:24 schrieben Sie:

> The only difference between subversion and other SCM systems
> is that other systems offer support for labeling and adding useful info
> to those revisions, while Subversion doesn't.

Which useful info besides the name, and always present things like a
revision, timestamps, who made the commit etc. is this? And how does
one benefit of those additional info compared to the lack of
structuring of branches and tags those SCMs provide compared to

> If you are referring to the ad-hoc method of copying the trunk/branch to
> a subdirectory then all that you're doing is copying the trunk directory
> to another directory in your repository. That may be a convenient hack,
> but that isn't exactly support for tagging.

That's not an argument at all, because all one does in other SCMs is
creating branches and tags. What you really should argue is what all
devs think is common sense about branches and tags and why Subversion
doesn't fulfill those requirements. The only thing mentioned until
now is that revision numbers can change in the way subversion handles
branches and tags and that only because Subversion does provide
features, like (re)structuring branches and tags in a hierarchical
way, other SCMs simply doesn't provide.

> Let's put it this way: if that was actually a tag then it could also be
> argued that any file system supports branching/tagging.

You ignore the versioning part of Subversion and that it guarantees
the state/history of branches and tags like any other SCM. Besides
that, from my understanding filesystems do provide something which
could be argued as support for branches and tags because branches are
simply just work on something based on something other, which is
implemented as copying files and directories, and tags are something
which isn't as worked on as on branches, but is based on something
other, too, and may easily be implemented using copying things around
again and simply don't touch it anymore or e.g. using snapshots, which
would better guarantee an unchanged content.

Filesystems with snapshots for tags would again provide benefits over
SMCs like git and their branching and tagging facilities because the
user has more flexibility in organizing his contents.

Mit freundlichen Grüßen,

Thorsten Schöning

Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Received on 2013-05-18 19:33:42 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.