You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Michael Brouwer <mb...@gmail.com> on 2007/03/11 15:50:06 UTC
Sparse WC management APIs (was: Re: Subversion 1.5)
I guess that's a disadvantage of the current design, in the svk model you
can make a tree sparse just by removing subtrees, directories or files, svk
update won't bring things back that the user deleted, only svk revert will.
Perhaps a combination of the current sparse tree code augmented with this
addition would make it possible to complete the feature quicker.
Michael
On 3/10/07, David Anderson <da...@natulte.net> wrote:
>
> Because the WC metadata for the parent directory will have recorded
> that the 'API' directory should be present, and will restore it on the
> next update. You need to update the metadata of the parent directory
> to say that you don't want the directory for it to be skipped on
> update.
>
> - Dave
>
> On 3/10/07, Michael Brouwer <mb...@gmail.com> wrote:
> > Why won't the rm -rf subdir "API" work for that?
> >
> > Michael
> >
> >
> >
> > On 3/9/07, Karl Fogel <kfogel@red-bean.com > wrote:
> > > "Mark Phippard" <markphip@gmail.com > writes:
> > > > Are you aware that the sparse directories feature you would get in
> > > > one month will only exist as API inside the Subversion libraries?
> > > > In other words, there will be no command line UI to use the feature.
> > > > You would have to do something yourself that uses the API or hope
> > > > that one of the GUI clients tackles the feature.
> > > >
> > > > The command line UI will come, but at best around the same time that
> > merge
> > > > tracking will be done.
> > > >
> > > > I would imagine if you created something that let you create a
> working
> > copy
> > > > that uses this feature that commands like update would respect it
> and
> > work
> > > > properly. Not sure of that though.
> > >
> > > I may have been overly gloomy in some of my posts on this.
> > >
> > > Some of the UI will be there -- in particular, sparse initial
> > > checkouts should be there, they're trivial once the APIs are in. But
> > > there won't yet be an interface for (say) removing a directory after
> > > you've expanded it.
> > >
> > > -Karl
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > dev-unsubscribe@subversion.tigris.org
> > > For additional commands, e-mail: dev-help@subversion.tigris.org
> > >
> > >
> >
> >
>
Re: Sparse WC management APIs
Posted by Karl Fogel <kf...@red-bean.com>.
"Michael Brouwer" <mb...@gmail.com> writes:
> I guess that's a disadvantage of the current design, in the svk model
> you can make a tree sparse just by removing subtrees, directories or
> files, svk update won't bring things back that the user deleted, only
> svk revert will.
>
> Perhaps a combination of the current sparse tree code augmented with
> this addition would make it possible to complete the feature quicker.
I think that's mainly a UI discussion; we could add that behavior any
time. It's just that for some people, bringing back "missing"
directories is a feature, not a bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org