At long last, here are the svn versions of the p4-bash scripts. Please review and comment... this is one of the last steps between us and subversion!
SYNOPSIS:
source svn-bash.sh
SEE ALSO:
openlaszlo/tools/trunk/env/setup-lps.sh
All svn commands operate on the current directory, the contents of
the current
directory, and all descendants of the current directory, unless
otherwise
specified.You, the developer, are responsible for maintaining a change description. To
create an empty change description, do
$ empty-change-description
This will create an empty change description in the /tmp directory.
You can
leave it there, or copy it into somewhere you want to take care of it.The output will be the name of the temporary file created, and the name will be in the shell variable $OL_CHANGE_DESCRIPTION, so you can edit the newly created
change description with
$ empty-change-description ; $EDITOR $OL_CHANGE_DESCRIPTION
If you
$ cp `empty-change-description` mychangemessage.txt
To edit a change description, if you have used the automatically created
change filename, do
$ svn-editchange
which will invoke $EDITOR on the file in $OL_CHANGE_DESCRIPTION. If
you're
managing the change description yourself, invoke your editor however
you like.
To create a change package, do
$ svn-makechangepackage
A tar file named patch.tar.XXXX will be created in the current working
directory, where XXXX is a unique identifier. (It's only unique of
files in the
director you're in; other developer's changesets might have the same
name.)
To send changes for review:
$ svn-review
or
$ svn-review mychangedescription.txt
On the mac, this will open a message in Mail. On other platforms, it
will print
a mailto url. Attach the changepackage to that message, and send.
To apply a change from another developer
cd to the right place (details to follow)
$ tar xvf patch.tar.XXXX (where XXXX is the actual patch unique id)
$ ./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 --file $OL_CHANGE_DESCRIPTION
or if you've got your change message in a file you're managing
$ svn commit --file mychangedescription.txt
Helper Functions
$ svn-changed
prints a list of locally modified and added files in this directory
and its
descendants
$ svn-verbose-status
prints the status of the files in the directory, grouped with
description of
the status, in case status K doesn't mean anything to you. The pure svn
invocation is just
$ svn status -v
The opposite of verbose is quiet, of course, so
$ svn status -q
prints not-much information, leaving out all the files not managed by
svn.
svn-bash.sh
Description: Binary data
_______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
