Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

SVNChecker 0.2.1 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News SVNChecker 0.2.1 (Default branch)
# 1  
Old 07-16-2008
SVNChecker 0.2.1 (Default branch)
ImageSVNChecker is a framework for Subversionpre-commit hooks in order to implement checks ofthe to-be-committed files before they arecommitted. For example, you can check for the codestyle or unit tests. The output of the checks canbe send by mail, written to a file, or simplyprinted to the console.License: The Apache License 2.0Changes:
This release fixes a couple of bugs. A bug in the pylint check that made the check pass although it failed was fixed. The "Pylint.ConfigFile" configuration option was made optional, and a default pylintrc will be used if you don't specify it. A bug in the transaction module that returned an empty file when calling getFile() more than once was fixed. A bug in the transaction module to avoid a deadlock when receiving big files was fixed. The SVNChecker was made compatible with Python 2.4.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT CENTOS

git-cherry

GIT-CHERRY(1)							    Git Manual							     GIT-CHERRY(1)

NAME

       git-cherry - Find commits not merged upstream

SYNOPSIS

       git cherry [-v] [<upstream> [<head> [<limit>]]]

DESCRIPTION

       The changeset (or "diff") of each commit between the fork-point and <head> is compared against each commit between the fork-point and
       <upstream>. The commits are compared with their patch id, obtained from the git patch-id program.

       Every commit that doesn't exist in the <upstream> branch has its id (sha1) reported, prefixed by a symbol. The ones that have equivalent
       change already in the <upstream> branch are prefixed with a minus (-) sign, and those that only exist in the <head> branch are prefixed
       with a plus (+) symbol:

		      __*__*__*__*__> <upstream>
		     /
	   fork-point
		     \__+__+__-__+__+__-__+__> <head>

       If a <limit> has been given then the commits along the <head> branch up to and including <limit> are not reported:

		      __*__*__*__*__> <upstream>
		     /
	   fork-point
		     \__*__*__<limit>__-__+__> <head>

       Because git cherry compares the changeset rather than the commit id (sha1), you can use git cherry to find out if a commit you made locally
       has been applied <upstream> under a different commit id. For example, this will happen if you're feeding patches <upstream> via email
       rather than pushing or pulling commits directly.

OPTIONS

       -v
	   Verbose.

       <upstream>
	   Upstream branch to compare against. Defaults to the first tracked remote branch, if available.

       <head>
	   Working branch; defaults to HEAD.

       <limit>
	   Do not report commits up to (and including) limit.

SEE ALSO

       git-patch-id(1)

GIT

       Part of the git(1) suite

Git 1.8.3.1							    06/10/2014							     GIT-CHERRY(1)