I'm also +1 to this feature.
I understand that svn_depth_exclude should be associated to a checked out
folder and set differently to other folders to build local working copy
custom structure.
A svn_depth_exclude_pattern set on checkout could help deciding which value
use on svn_depth_exclude for other folders found when checking out. So, if
the desired working copy structure follows a excluding logic, it will be
automatically built on a single command.
The update command should also check the same local
svn_depth_exclude_pattern to decide which value to use for svn_depth_exclude
for each new folder added by other users.
Another parameter could be used for setting default
svn_depth_exclude_pattern saved as a folder property on the repository, so
that any checkout that doesn't specify a custom pattern will use this
"default" custom exclusion pattern for the folder. Patterns set locally
prevails over repository patterns.
An include pattern can prevail over the exclude pattern to bring specific
folders, excluded by default, but needed at that time.
Ps: I have lots of software repositories that contains a default folder tree
for system documentation, source code and change requests. Checking out the
root of this structure simplifies a lot, but brings all change requests.
Users are interested in all documentation and in a specific change request
folder, not all. I would love this feature!
Luiz Guilherme M. Kimel
-----Mensagem original-----
De: Autumn [mailto:dsjstc_at_gmail.com]
Enviada em: sexta-feira, 10 de setembro de 2010 12:28
Para: Daniel Shahaf
Cc: Itamar O; users_at_subversion.apache.org
Assunto: Re: Checkout exclude pattern
Cool, that hadn't occured to me. That could mean that no structural
changes are required to the .svn format -- only a code change to the
checkout logic to preemptively create the exclude entries.
I'm not sure how it would handle the case where someone else adds new
files which match my pattern, for which no svn_depth_exclude entry yet
exists.
Ideas?
> I think under the hood, such a --exclude option would be implemented by
> setting the depth of the files-matching-the-pattern to svn_depth_exclude.
> So I'm asking if the desired feature is to be able to set that depth at
> checkout time, before the files are fetched even once.
Received on 2010-09-10 17:53:08 CEST