You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Chris <su...@softegg.org> on 2007/10/24 08:02:31 UTC

Working on a subset of a directory

Hi!

I co-worker lately came with the question if it is possible to work
(locally) only on a subset of directories. This works fine using the
'-N' parameter when checking out a top dir and then updating just the
subdirs he is interested in:

$ svn co -N REPO/top ~/top
$ cd ~/top
$ svn up dir1 dir4     # assume we have dir1 ... dir5 under top

Now, whenever he does a 'svn st' only changes in dir1 and dir4 are
reported (dir2, dir3 and dir5) are not mentioned at all by svn. So far
so good.

At some point he might *temporarily* be interested also in an
additional subdir, ie.

$ cd ~/top
$ svn up dir3

After fixing some stuff in that dir, he want to (locally) get rid of
it. The problem: If he removes it (with 'rm -rf dir3') the svn status
command reports that dir3 is missing:

$ cd ~/top
$ svn st
! dir3

The other dirs (dir2 and dir5 - never updated before) are still not
reported.

Is there any way (other than removing 'dir3' from the .svn/entries
file) to tell svn that we are not interested in 'dir3' anymore?

Thanks alot!
--
chris
--
chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Working on a subset of a directory

Posted by Erik Huelsmann <eh...@gmail.com>.
On 10/24/07, Chris <su...@softegg.org> wrote:
> Hi!
>
> I co-worker lately came with the question if it is possible to work
> (locally) only on a subset of directories. This works fine using the
> '-N' parameter when checking out a top dir and then updating just the
> subdirs he is interested in:
>
> $ svn co -N REPO/top ~/top
> $ cd ~/top
> $ svn up dir1 dir4     # assume we have dir1 ... dir5 under top
>
> Now, whenever he does a 'svn st' only changes in dir1 and dir4 are
> reported (dir2, dir3 and dir5) are not mentioned at all by svn. So far
> so good.
>
> At some point he might *temporarily* be interested also in an
> additional subdir, ie.
>
> $ cd ~/top
> $ svn up dir3
>
> After fixing some stuff in that dir, he want to (locally) get rid of
> it. The problem: If he removes it (with 'rm -rf dir3') the svn status
> command reports that dir3 is missing:
>
> $ cd ~/top
> $ svn st
> ! dir3
>
> The other dirs (dir2 and dir5 - never updated before) are still not
> reported.
>
> Is there any way (other than removing 'dir3' from the .svn/entries
> file) to tell svn that we are not interested in 'dir3' anymore?

It's currently not really possible to do that. This will change in 1.5
with a feature called 'sparse directories'. We're working our butts of
to get 1.5 done, but when it's done, I can't tell yet.

bye,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org