community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ross Gardler (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COMDEV-32) Subversion: Viewspecs
Date Sun, 04 Jul 2010 01:03:50 GMT

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

Ross Gardler updated COMDEV-32:
-------------------------------

    Component/s: Mentoring
                     (was: Comdev)

> Subversion: Viewspecs
> ---------------------
>
>                 Key: COMDEV-32
>                 URL: https://issues.apache.org/jira/browse/COMDEV-32
>             Project: Community Development
>          Issue Type: Task
>          Components: Mentoring
>            Reporter: Stefan Sperling
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message