On 4/22/07, eg <email@example.com> wrote:
> Make sure you read the section in the manual regarding "Vendor Branches"
Thanks I did read (actually make that skimmed) that section, but
didn't see it applying to my situation at the time.
I'll go back and have a look thinking how I can use those features.
In the meantime I've gotten started - I HIGHLY recommend doing
something like this as a way to learn how to use Subversion for
Here's how far I've gotten so far:
X:\xampp>svn list svn://localhost/tags
None of this has any of "my stuff" in it yet, and trunk is still at r1.
At one point I checked out the full TTB tree from the root and it was
nearly 3GB - I'd messed up some of my moves and copies using URLs and
thought it would be easier to work with the tree locally and then
commit it back up.
Won't make THAT mistake again!
The total space taken by the repository with all these versions is
still under 90MB, less than a single regular backup of XAMPP - what a
One thing I found very puzzling - what is the logic behind making a
copy from trunk to tags increment the revision number? The actual
content doesn't change. . .
BTW the Tortoise shell extensions (specifically the cache) seemed to
be the cause of major slow-downs, basically a crash and corruption -
maybe eating too much memory? So I disabled them.
Anyone recommend another particular Windows GUI front-end, one that's
only active when I actually want it to be?
The hotcopy backups are very handy. . .
And actually I HIGHLY recommend using Subversion as a sysadmin tool
for managing any complex software system where you'd usually be
hesitant to upgrade to the "latest and greatest" version of something
because you've done customisations. In my case I think I'll be using
it with WordPress and (when I'm ready) whatever CMS I start to learn -
drupal, joomla xoops.
It's definitely useful for a much wider audience than programmers
looking after their codebase.
My school (300+ staff) is currently engaged in forming about 20
different committees to write a large set of "mission/vision/process"
type documentation for the process of accreditation, and I can really
see how doing it all through svn would make it a much more efficient
process, reducing the need for them to actually do the writing during
meetings (what a ridiculously boring way to do it eh?).
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Apr 22 13:52:27 2007