Re: version control model of Subversion source code

> On Mar 20, 2019, at 11:25 PM, Daniel Shahaf wrote: > > I think wuzhouhui wasn't asking about branching models in general, but > specifically about what model the Subversion project uses for versioning > its own source code (https://svn.apache.org/repos/asf/subversion/). Right, this is what I

version control model of Subversion source code

Hi, This question is unrelated to Subversion's usage or issues, but related to version control model of Subversion source code. Let me explain in detail. As far as I know, new code is committed to trunk firstly, then cherry-picked to release-branch in necessary, so the branch-view of Subversion

Re: version control model of Subversion source code

* wuzhouhui: > As far as I know, new code is committed to trunk firstly, then > cherry-picked to release-branch in necessary [...] And tags are > always created on release-branch. It can be done this way, but that's not a requirement. One can also tag 'trunk', or any other branch. -Ralph

Re: version control model of Subversion source code

I think wuzhouhui wasn't asking about branching models in general, but specifically about what model the Subversion project uses for versioning its own source code (https://svn.apache.org/repos/asf/subversion/). wuzhouhui, your description is accurate. In Subversion's tree changes are committed

Re: version control model of Subversion source code

You can do any branching model you like with subversion. That said, I maintain that Trunk-Based Development is the best model, and note that there are merge issues with other branching models in rare circumstances [ ref

svn up --set-depth exclude takes very long time

Hi, having a very big working copy (>100GB) want to exclude “folderA” (~2.5GB) from this wc via “svn up –set-depth exclude folderA” . This command takes very long time – did not finish after 2 days when doing this on a NFS mounted dir. Even when the wc is on a local disk, it takes very long time

Re: File capacity limitation in theory in SVN

Redirecting this to the users@ list where it is more appropriate. On Wed, Mar 20, 2019 at 7:33 AM sosogh wrote: > Hi list > > There are about 1.65T , 2.72 million files ，274 thousand folders in Samba. > It consist of any file types : txt , bin , pic , audio , video and so on . > We are

Re: svn up --set-depth exclude takes very long time

On Wed, Mar 20, 2019 at 8:46 PM Pavel Lyalyakin < pavel.lyalya...@visualsvn.com> wrote: > Hello Holger, > > On Wed, Mar 20, 2019 at 2:33 PM Weiss, Holger < > holger.we...@continental-corporation.com> wrote: > > > > Hi, > > > > having a very big working copy (>100GB) want to exclude “folderA” >

Re: svn up --set-depth exclude takes very long time

Hello Holger, On Wed, Mar 20, 2019 at 2:33 PM Weiss, Holger < holger.we...@continental-corporation.com> wrote: > > Hi, > > having a very big working copy (>100GB) want to exclude “folderA” (~2.5GB) from this wc via “svn up –set-depth exclude folderA” . > This command takes very long time – did

Re: File capacity limitation in theory in SVN

Mark Phippard wrote on Wed, 20 Mar 2019 11:53 +00:00: > * While there are no limits on number of files or total size, Not to nitpick, but since there's no such thing as "unlimited capacity", let me be one level more accurate: Internally Subversion stores file size using signed 64-bit integers,

Re: File capacity limitation in theory in SVN

Soso, I've tested Subversion up to 4TB myself (one repo), with the intention of using https://github.com/subsyncit/subsyncit with it for corporate file sync. That is still a work in progress, as it happens. - Paul On Wed, Mar 20, 2019 at 11:53 AM Mark Phippard wrote: > Redirecting this to the

Re: File capacity limitation in theory in SVN

On Wed, Mar 20, 2019 at 7:53 AM Mark Phippard wrote: > > Redirecting this to the users@ list where it is more appropriate. > > On Wed, Mar 20, 2019 at 7:33 AM sosogh wrote: >> >> Hi list >> >> There are about 1.65T , 2.72 million files ，274 thousand folders in Samba. >> It consist of any file