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

Request for enhancement to have update command and others support svn:ignore

From: Tardif, Sebastien <STARDIF_at_anacomp.com>
Date: 2005-03-30 22:25:09 CEST

This is a request for enhancement to have update command and others
support svn:ignore.

So I could do this with the scenario described in previous email:
svn update --config-dir noEclipseWorkspace

The configuration in noEclipseWorkspace will then specify that
svn:ignore has directory "EclipseWorkspace".

What do you think?

We can then support other scenario:
- take UI stuff only
- take Java stuff for this project but not C++
- take Java stuff but only modules I'm working on
...

-----Original Message-----
From: Tardif, Sebastien [mailto:STARDIF@anacomp.com]
Sent: Wednesday, March 30, 2005 9:15 AM
To: users@subversion.tigris.org
Subject: What's the best practice to update many directories but
excluding some?

What's the best practice to update many directories but excluding some?

For example let say I have many scenarios so I cannot have a fix layout
that match all of them.

In one case I have this:

Java
        UI
        EJB
        Servlet
        XML
        EclipseWorkspace

I want to update everything under Java except EclipseWorkspace.

How people do this?

Call svn update 4 times for every one (UI, EJB, Servlet, XML) ?

Use a custom shell script?

Use some "special" subversion feature?

Can we use your "trick" with other commands than "update"?

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 30 22:26:23 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.