making svn status ignore externals

[Daniel Schlyder <da...@bitblaze.com>]

Hi list,

Is it possible to make 'svn status' not report status of externals?

I usually use svn:externals to fetch tags, so status is, naturally, of litte
interest. If there is no such way (or even if there is -- IMHO, this would
still be a good idea), maybe svn:ignore could be used for this, just like you,
prior to 'svn status' being changed, could add external dirs to this property
to avoid them showing up as question marks?


Regards,
Daniel Schlyder


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

Re: making svn status ignore externals

[Daniel Schlyder <da...@bitblaze.com>]

[19.11.2003 01:10:13] Ben Collins-Sussman:
> You see where I'm heading here.  If you want svn:externals to be ignored
> by recursive operations, why use the feature at all?  Just checkout a
> bunch of working copies, and nest them in each other.  You can write a
> tiny shell script (for your developers) that 'bootstraps' by doing a few
> checkouts.

Yeah, I see I've been using svn:externals incorrectly. Thanks for the
clarification. Please ignore my previous mail.

Regards,
Daniel Schlyder


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

Re: making svn status ignore externals

[Ben Collins-Sussman <su...@collab.net>]

On Tue, 2003-11-18 at 17:46, Daniel Schlyder wrote:
> Hi list,
> 
> Is it possible to make 'svn status' not report status of externals?
> 
> I usually use svn:externals to fetch tags, so status is, naturally, of litte
> interest. If there is no such way (or even if there is -- IMHO, this would
> still be a good idea), maybe svn:ignore could be used for this, just like you,
> prior to 'svn status' being changed, could add external dirs to this property
> to avoid them showing up as question marks?

I don't understand the motivation here.  Either you have a "single
virtual working copy" made out many different working copies, or you
don't.  

You don't want 'svn status' to traverse externals, because you just
fetch tags.  By that argument, shouldn't 'svn update' also ignore them,
since the tags never change?   And 'svn commit', as well, I guess,
right... ?

You see where I'm heading here.  If you want svn:externals to be ignored
by recursive operations, why use the feature at all?  Just checkout a
bunch of working copies, and nest them in each other.  You can write a
tiny shell script (for your developers) that 'bootstraps' by doing a few
checkouts.



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