community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shane Curcuru (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (COMDEV-32) Subversion: Viewspecs
Date Tue, 07 Nov 2017 01:36:00 GMT

     [ https://issues.apache.org/jira/browse/COMDEV-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shane Curcuru closed COMDEV-32.
-------------------------------
    Resolution: Unresolved

Closing really old GSOC issues; feel free to reopen if still needed.

> Subversion: Viewspecs
> ---------------------
>
>                 Key: COMDEV-32
>                 URL: https://issues.apache.org/jira/browse/COMDEV-32
>             Project: Community Development
>          Issue Type: Task
>          Components: GSoC/Mentoring ideas
>            Reporter: Stefan Sperling
>              Labels: gsoc, mentor
>
> Subversion currently supports some mechanisms for selectively building
> and populating a working copy, including sparse directory support and
> externals definitions. What Subversion lacks is a handy way to be told —
> in one easy step — to go off and make use of those underlying features
> to build a working copy that looks some specific way. Imagine being able
> to tell new developers on your project to checkout a working copy using
> some pre-formulated specification which results in an automated sparse
> checkout that includes your trunk, branches, and then various branches
> for the currently maintained versions of your software
> (branches/SOME-VERSION), instead of having to tell them to first do a
> --depth=empty checkout of the root, then a --set-depth=infinity update
> of trunk and branches, then..



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org


Mime
View raw message