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

Re: RES: Checkout exclude pattern

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Thu, 23 Sep 2010 19:24:56 +0200

Does this help? (at the moment it doesn't support patterns)

https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/svn-viewspec.py

Luiz Guilherme Kimel wrote on Thu, Sep 23, 2010 at 12:28:14 -0300:
> Any news about this or everybody forgot about it?
>
> -----Mensagem original-----
> De: Daniel Shahaf [mailto:d.s_at_daniel.shahaf.name]
> Enviada em: sexta-feira, 10 de setembro de 2010 13:09
> Para: users_at_subversion.apache.org
> Assunto: Re: Checkout exclude pattern
>
> If the 'checkout' logic can tell the server to not send some files, then
> so can the 'update' logic. It's just a matter of making it remember to
> do that. (i.e., having the exclude pattern persist somewhere and used
> by the 'update' command)
>
> Autumn wrote on Fri, Sep 10, 2010 at 08:27:34 -0700:
> > 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-23 19:29:15 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.