Differences between revisions 1 and 4 (spanning 3 versions)
⇤ ← Revision 1 as of 2007-08-04 14:50:43 →
Size: 3410
Editor: ZoomQuiet
Comment:
← Revision 4 as of 2009-12-25 07:16:41 → ⇥
Size: 1009
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
::-- ZoomQuiet [[[DateTime(2007-08-04T14:50:43Z)]]]
[[TableOfContents]]		 ::-- ZoomQuiet [<<DateTime(2007-08-04T14:50:43Z)>>]
<<TableOfContents>>
Line 9: Line 9:
[[Include(CPUGnav)]] <<Include(CPUGnav)>>
Line 24: Line 24:
# The default working directory for the invocation is undefined, so
# the program should set one explicitly if it cares.
#
# If the hook program exits with success, the txn is committed; but
# if it exits with failure (non-zero), the txn is aborted, no commit
# takes place, and STDERR is returned to the client. The hook
# program can use the 'svnlook' utility to help it examine the txn.
#
# On a Unix system, the normal procedure is to have 'pre-commit'
# invoke other programs to do the real work, though it may do the
# work itself too.
#
# *** NOTE: THE HOOK PROGRAM MUST NOT MODIFY THE TXN, EXCEPT ***
# *** FOR REVISION PROPERTIES (like svn:log or svn:author). ***
#
# This is why we recommend using the read-only 'svnlook' utility.
# In the future, Subversion may enforce the rule that pre-commit
# hooks should not modify the versioned data in txns, or else come
# up with a mechanism to make it safe to do so (by informing the
# committing client of the changes). However, right now neither
# mechanism is implemented, so hook writers just have to be careful.
#
# Note that 'pre-commit' must be executable by the user(s) who will
# invoke it (typically the user httpd runs as), and that user must
# have filesystem-level permission to access the repository.
#
# On a Windows system, you should name the hook program
# 'pre-commit.bat' or 'pre-commit.exe',
# but the basic idea is the same.
#
# The hook program typically does not inherit the environment of
# its parent process. For example, a common problem is for the
# PATH environment variable to not be set to its usual value, so
# that subprograms fail to launch unless invoked via absolute path.
# If you're having unexpected problems with a hook program, the
# culprit may be unusual (or missing) environment variables.
#
# Here is an example hook script, for a Unix /bin/sh interpreter.
# For more examples and pre-written hooks, see those in
# the Subversion repository at
# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and
# http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/
Line 82: Line 41:
= 文章大标 =
''简述''
== 章标题1 ==

=== 小节标题1 ===
{{{
#!python
Python code
}}}

==== 次节标题1 ====
xxx

== 章标题2 ==

=== 小节标题2 ===
{{{
其它
代码引用
}}}

==== 次节标题2 ====
yyy
Line 107: Line 43:
[[PageComment2]]

通过定制 pre-commit 禁止提交空注释的代码 ::-- ZoomQuiet [2007-08-04 14:50:43]

Contents

  1. 反馈

CPUG联盟::

CPUG::门户plone

BPUG

SPUG

ZPUG

SpreadPython Python宣传 

# PRE-COMMIT HOOK
#
# The pre-commit hook is invoked before a Subversion txn is
# committed.  Subversion runs this hook by invoking a program
# (script, executable, binary, etc.) named 'pre-commit' (for which
# this file is a template), with the following ordered arguments:
#
#   [1] REPOS-PATH   (the path to this repository)
#   [2] TXN-NAME     (the name of the txn about to be committed)
#


REPOS="$1"
TXN="$2"
# Make sure that the log message contains some text.
SVNLOOK=/usr/local/bin/svnlook
$SVNLOOK log -t "$TXN" "$REPOS" | \
   grep "[a-zA-Z0-9]" > /dev/null 

if [ $? != 0 ]; then
        echo "$TXN $REPOS" 1>&2
        echo "Alert! Commit message can not be empty." 1>&2
        exit 1
fi

exit 0

1. 反馈

SubVerSion/AntiEmptyCi (last edited 2009-12-25 07:16:41 by localhost)