Wilfredo Sánchez Vega <email@example.com> writes:
> I've got some scripts to submit to the contrib/ folder, if y'all
> want them:
> I think this does the same stuff as the svn-apply-autoprops.py
> that's already there, except:
Note: current one is "svn_apply_autoprops.py", that is, underscores
and a ".py" ending, contrasted with your "svn-apply-autoprops".
> - it uses python's ConfigParser module rather than implementing
> it's own
> - it's BSD licensed instead of GPL
> - has some options:
> - "dry run" mode
> - choose an alternative config file
> - clear properties if not in config or if empty in config
In view of the increased functionality and use of ConfigParser, I'd be
okay with replacing the current one with this new one, but it would be
nice to get Blair Zajac's thoughts on that first (just a courtesy
ping, if nothing else, since he wrote the original). I've CC'd him on
this mail. Blair?
> View diffs using FileMerge (OS X). You can use FileMerge to undo
> specific changes in the wc. (I find it useful for quickly removing
> debug code before commits.)
I don't think the "--help" option on that one is quite working:
$ ls -l ~/etc/svn-viewdiff
-rwxr-xr-x 1 kfogel kfogel 4515 Mar 15 15:21 /home/kfogel/etc/svn-viewdiff*
$ head ~/etc/svn-viewdiff
# -*- coding:utf-8;mode:shell-script;mode:font-lock -*-
# GNU diff wrapper for FileMerge.
# Copyright (c) 2002 Wilfredo Sanchez Vega <firstname.lastname@example.org>.
# All rights reserved.
# Permission to use, copy, modify, and distribute this software for any
diff: missing operand after `diff'
diff: Try `diff --help' for more information.
[Hmm, that error message is from diff itself, not your script!]
$ ~/etc/svn-viewdiff --help
Usage: diff [OPTION]... FILES
Compare files line by line.
[...rest of help for GNU 'diff' here...]
Report bugs to <email@example.com>.
> Resolve merge conflicts using FileMerge (OS X).
This one has no online help, beyond the line quoted above.
Documentation is especially important in contrib/ scripts, where
people often just browse around seeing if what they need is there.
> This is a pre-commit hook script. It lets you specify some
> enforcement rules on commits at the diff level.
> Meaning, you can disallow a commit because it added a line of code
> you don't like, but not because the file already has an offending
> line (eg. don't make it worse).
> Or you can fail a commit because it didn't clean up junk in a file
> it edited, if that's your style.
> Bunch of other stuff if you get creative. You'll want to read the
> __doc__ string in the script and look at the example config file if
> you want ore details.
Nice documentation! Suggest renaming 'enforcer.conf' to
EXAMPLE-enforcer.conf or something similar, though.
I'm +1 on your maintaining all these in contrib/, if you can make them
www.collab.net <> CollabNet | Distributed Development On Demand
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Mar 15 21:42:33 2006