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

RE: Re: Strategies for projects/branches layout

From: Jesse Erlbaum <jesse_at_erlbaum.net>
Date: 2005-11-07 23:43:26 CET

Hi Josh --

> Unless you want to check out the whole repos, you will not be able to
> get atomic commits across projects, since svn co -N is currently
> broken.

If I understand what you're saying here, because there is no "trunk/"
directory it won't be possible to check out all the projects at once, or
to commit changes to all at once. Is that right?

Couldn't I just check out the CLIENT_A directory (including the tags and
branches directories)?

> Also hand building branches like you are talking about can be
> disk intensive since they'll need to be done client-side, unless you
> feel like using some scripting tools to combine multiple commands
> into a single transaction (for which there are tools).

Couldn't I just copy the files in my WC, and commit all at once?

That being said, you know what I'd really like: Command line "svn copy"
and "svn move" which works like the shell commands they're based on:

  svn copy file1 file2 file3 filen dest_dir/
  svn move file1 file2 file3 filen dest_dir/

Just a thought.

> But in the end, it is whatever fits your workflow best. Work is
> currently underway to fix non-recursive checkouts, so that may
> not be an issue for long.

How do you see broken non-recursive checkouts causing a problem in the
scheme I'm describing?



Jesse Erlbaum
The Erlbaum Group
Phone: 212-684-6161
Fax: 212-684-6226
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 7 23:46:12 2005

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.