[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Feature request: Really verbose status information

From: Ryan Schmidt <subversion-2008b_at_ryandesign.com>
Date: Tue, 24 Jun 2008 01:36:28 -0500

On Jun 23, 2008, at 07:55, Holger Hellmuth wrote:

> David Weintraub schrieb:
>> I have a PHP script that does my Subversion log for most of my users
>> (even the developers). I use the "--xml" parameter and then use a
>> style sheet to format the log output. It would be pretty easy to
>> add a
>> key to the statuses on that log.
> Excellent idea. If you can part with a copy of your script, I would
> be interested. Sadly
> this means remembering a separate command for status reports, this
> is not much different
> from telling my users to use 'svn help status'. Easily forgotten a
> month later.

Shell functions, shell aliases or wrapper scripts can help.

For example, I never want to see the diff of a deleted file, but
Subversion shows one unless you use --no-diff-deleted. Also,
Subversion doesn't show diffs correctly if the file in question does
not have Unix linefeeds (at least that's been my experience). So I
use an external diff command which first transforms all files to Unix
linefeeds before running /usr/bin/diff on them. (By the way, if
someone has a better way to make this work, I'd love to hear it.)

To make this the default for me, without having to remember anything
new, I have the following function in my ~/.bash_profile. You could
do something similar for your users, overriding "svn st|stat|status"
but passing everything else through unchanged.

svn() {
        case "$1" in
                        command svn --no-diff-deleted --diff-cmd mydiff "$@"
                        command svn "$@"

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-24 08:36:52 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.