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

Re: Need help with multiple commits instead of one ?

From: Ryan Schmidt <subversion-2006q2_at_ryandesign.com>
Date: 2006-05-19 12:18:43 CEST

On May 19, 2006, at 11:41, Denis Koelewijn wrote:

> \branches
> \tags
> \trunk
> \core
> \productA_shared
> \productA_webapp1
> \productA_webapp2
> \productB_shared
> \productB_webapp1
> \productB_webapp2
>
> When I work on projectA, in need \core, and all the productA_xxx
> projects. So I check out only these projects in Eclipse (or
> TortoiseSVN). Then if I want to commit changes over these projects
> in one commit, I see that Eclipse (and TortoiseSVN) use multiple
> commits, one for every project. That's not behaviour that I had
> expected, or what I want.
>
> What I noticed is that on my disk in the parent directory where the
> projects are checkout to, no .svn directory exist, only in the
> project directories themselves.
>
> Anyone an idea how I can change this behaviour ? I use Subversion
> 1.3.1, TortoiseSVN 1.3.3, Eclipse 3.1.2 and Subclipse v1.0.1 on
> Windows XP Pro.

Check out the entire trunk.

If that's too much for you, check out trunk non-recursively, then
update the directories you want. Note that non-recursive checkouts
are somewhat broken and may or may not work the way you need them to.

Another option is to check out the entire trunk, then "svn switch"
the directories you do not need to an empty directory in the
repository, which you could create specifically for this purpose. The
initial checkout will still take a lot of time and disk space, but
after switching the unneeded directories to the empty directory,
it'll be smaller again, and subsequent updates will be faster.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 19 12:19:57 2006

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

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