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:
> C
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 patte
Itamar O wrote on Fri, Sep 10, 2010 at 14:32:54 +0300:
> On Fri, Sep 10, 2010 at 2:05 PM, Daniel Shahaf wrote:
>
> > So, you want a way to do
> >
> >svn up --set-depth=exclude $file
> >
> > at checkout time?
> >
>
> I think the desired behavior is not related to set-depth.
> something lik
On Fri, Sep 10, 2010 at 2:05 PM, Daniel Shahaf wrote:
> So, you want a way to do
>
>svn up --set-depth=exclude $file
>
> at checkout time?
>
I think the desired behavior is not related to set-depth.
something like:
svn [up,co] --exclude
so you could also use set-depth, if relevant.
I'
So, you want a way to do
svn up --set-depth=exclude $file
at checkout time?
Ds Jstc wrote on Thu, Sep 09, 2010 at 19:22:02 -0700:
> I use subversion to remotely participate in a project with gigs of
> frequently-changing files that never affect me, mostly images and
> localizations.
