On 11/7/05, Jesse Erlbaum <email@example.com> wrote:
> 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)?
Yes that works, I was interpreting CLIENT_A as the repos name,
my mistake. However this does leave you checking out the
branches and tags which will be a lot of code to check out.
> > 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?
Yes that is exactly what you will have to do, which requires enough
disk space for multiple copies of your codebase.
> 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/
A patch for this was just submitted and is going through review, so
this may be done soon (well 1.4 maybe).
> > 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?
If you could do a non-recursive checkout, you could check out just
the projects you were working on, without the branches or tags dir.
But doing this now leads to broken behavior, so you have to check out
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Nov 8 00:14:10 2005