5 This git repository took out the contributed post-receive hook
6 from git.git with its full history and aims to continue to fix
7 and develop it. There is also FusionForge/Evolvis integration,
10 This repository is hosted on evolvis.org (a public FusionForge
11 instance by tarent). We mirror it on github for popularity, as
12 shown below. Development of the hook is partially sponsored by
13 tarent, FreeWRT (now The MirOS Project), Teckids.
15 • https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=evolvis-platfrm/recvhook.git
16 • https://github.com/mirabilos/recvhook
18 Please do steer new contributions to Evolvis. Development will
19 be done in the “standalone” branch which can then be merged to
20 both “master” (for visibility) and “forge” (further integrati‐
21 ve and development work). Ensure the live branches and release
22 tags always only have the hook script (not this README file or
23 the LICENCE file) in them, since other repositories merge them
24 using the subtree strategy regularily.
27 • https://evolvis.org/
28 ‣ start page of the public Evolvis instance
29 • https://evolvis.org/projects/evolvis-platfrm/
30 ‣ project page for developing Evolvis itself
31 • https://fusionforge.org/
32 ‣ EvolvisForge’s upstream, FusionForge
33 • http://www.tarent.de/
34 ‣ tarent solutions GmbH, sponsoring part of this
35 • http://mako.cc/writing/hill-free_tools.html
36 ‣ why you should *not* be using github!
37 • http://mako.cc/copyrighteous/freedom-for-users-not-for-software
39 • https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html
40 ‣ merge this script into your own repository
46 This script is basically a replacement for the script
47 that came with git, except you will not see the annoying
48 “[SCM] ” præfix in eMails any more, and have to change
49 a few configuration settings:
51 • hooks.showrev ⇒ clear this, use our default
52 • hooks.diffopts ⇒ clear this, use our default
54 There are notable new settings:
56 • hooks.replyto (sets a Reply-To: header)
57 • hooks.shortdesc (used in the Subject: header instead
58 of the content of the description file)
59 • hooks.kgbconffile (full path to a configuration file
60 for kgb-client, triggers on-push IRC notifications)
62 There’s also noticeable effort to fix umlauts and
63 other nōn-ASCII characters in eMails – as long as
64 you use UTF-8 in your commits, of course.
66 For more information, please read the script directly.
67 If there will ever be frequently asked questions, I’ll
68 amend this documentation section though ☺
projects / fusionforge / fusionforge.git / blob