There is no way in heck that you will be able to do this stuff with
tortoise svn gui. These bash scripts are built on top of and around
the svn command line client.
Gregor and I just talked through how to meet his needs without these
tools -- an in-person review.
On Oct 25, 2006, at 11:37 AM, Michael Gregor wrote:
How to use subversion for OpenLaszlo collaborative development
author: benjamin shine [EMAIL PROTECTED]
last modified: 10.13.2006
SYNOPSIS:
source svn-bash.sh
SEE ALSO:
openlaszlo/tools/trunk/env/setup-lps.sh
Change descriptions in progress are stored in $SVNCHANGES. If you
do not
define and create $SVNCHANGES, it will be defined and created for you.
These commands rely on the shell variable $OL_CHANGE_NAME, which
is set by svn-newchange. The "change name" is the name of the
directory in
$SVNCHANGES which contains the change description. It looks like
20061013-ben-X where X is a uniquifying letter or number.
All svn commands operate on the current directory, the contents of
the current
directory, and all descendants of the current directory, unless
otherwise
specified.
To create a new change, do
$ svn-newchange
which will create a new change description in $SVNCHANGES and open
your
editor on that new change description.
To edit an existing change, do
$ svn-editchange
To send changes for review:
$ svn-review
or
$ svn-review <changename>
This makes the patch available in subversion, within the openlaszlo/
patches
directory, ie, http://svn.openlaszlo.org/openlaszlo/patches/
20061013-ben-X.tar
Note that this command checks your change in as a proposed change
to the patches
directory, for the purposes of review; it does not check in your
code to the
source tree itself.
On the mac, this will open a message in Mail. On other platforms,
it will print
a mailto url.
To apply a change from another developer
cd to the right place, uncompress and untar the change, then
$ ./apply.sh
To back out a change you applied, either
$ svn-unapplychangepackage
which is really just "apply this patch in reverse", equivalent to
$ patch -p0 -R -i difffile
To commit
$ svn-commit
or if you've got your change message in a file you're managing
$ svn-commit <changename>
What's out?
$ svn-pending
prints a list of local changesets, both committed and not-yet-
committed.
Recommended practices
Occasionally explicitly clean up committed changes in $SVNCHANGES.
