> -----Original Message-----
> From: Ryan Schmidt [mailto:firstname.lastname@example.org]
<snip stuff about badly organised project>
> Now, if [checking out the trunk]is inconvenient or impossible because
the entire trunk
> is so huge that it would take forever to check out or because
> it uses
> inordinate amounts of disk space on the client, then you'll have to
> work around that organizational problem by creating a branch that
> only contains what you want to work on.
Checking out the trunk wouldn't be realistic, no. I am asking the
developers to indicate functional groupings, and will try arranging the
trunk into functional subdirectories in a test area as an experiment.
However I suspect this won't work out in practice, but that's my
> For example...
> $ svn info $URL
> # see what the HEAD revision of the repository is -- let's
> say it's 456
> $ svn mkdir $URL/devrep/branches/issue123 \
> -m "making empty issue123 branch"
> $ svn cp -r456 $URL/devrep/trunk/foo $URL/devrep/branches/issue123 \
> -m "copying foo from trunk r456 to issue123 branch"
> $ svn cp -r456 $URL/devrep/trunk/bar $URL/devrep/branches/issue123 \
> -m "copying bar from trunk r456 to issue123 branch"
> $ svn cp -r456 $URL/devrep/trunk/baz $URL/devrep/branches/issue123 \
> -m "copying baz from trunk r456 to issue123 branch"
Perfect - this is exactly the procedure I needed to understand. I could
do this with tortoisesvn, but I wasn't sure how to accomplish the same
task on the command line.
> Yes, this is more work, and you end up with several revisions being
> required to accomplish what is logically a single task (that of
> creating the branch). But that's not such a big deal.
Quite. Very helpful indeed, and thanks also for other poster's
This e-mail and any files attached are strictly confidential, may be legally privileged
and are intended solely for the addressee. If you are not the intended recipient, note
that any disclosure, copying, distribution, or use of the contents of this message and
attachments is strictly prohibited. Please notify the sender immediately by return email,
phone or fax and then delete the e-mail and any attachments immediately. The views
and or opinions expressed in this e-mail are not necessarily the views of De La Rue plc
or any of its subsidiaries and the De La Rue Group of companies, their directors,
officers and employees make no representation about and accept no liability for its
accuracy or completeness. Please ensure you have adequate virus protection before
you open any attachment as the De La Rue Group of companies do not accept liability
for any viruses.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Dec 20 09:59:42 2006