38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
-
+
-
+
|
# "Rules" for Code Contributors
* When working on bits which themselves write to the repository, e.g. creating checkins, please be *exceedingly careful* not to corrupt the db :-D. The library has several layers of defense against the injection of problematic control artifacts, but still... be careful.
* Please try to conform to the rough overall coding style (as initially laid out by Fossil v1). We're not picky about whether or not spaces belong before/after an `if`, but the general overall style should be *more or less* uniform.
* Please build with the highest possible warning level and enable fatal warnings (in GCC and similar compilers: `-Wall -Werror -pedantic`).
* The trunk currently has no stability guarantees and is very much in flux, so feel free to work there instead of a branch if you like. Insofar as possible/reasonable, using libfossil's own [f-apps][] for working with the repository is recommended (e.g. using `f-checkin` to perform checkins).
* The trunk currently has no stability guarantees and is very much in flux, so feel free to work there instead of a branch if you like. Insofar as possible/reasonable, using libfossil's own [f-apps][] for working with the repository is recommended (e.g. using `f-ci` to perform checkins and `f-merge` for merging branches).
There is nothing holy or sacred about this repo, so feel free to hack at will. Most of the library's sanity tests are packaged in <tt>[f-sanity.c](/finfo?name=f-apps/f-sanity.c)</tt>. See <tt>[fossil-cli.h](/finfo?name=include/fossil-scm/fossil-cli.h)</tt> for a mini-framework to bootstrap new apps and [f-apps][].
There is nothing holy or sacred about this repo, so feel free to hack at will. Most of the library's sanity tests are packaged in <tt>[f-sanity.c](/finfo?name=f-apps/f-sanity.c)</tt>. See <tt>[cli.h](/finfo?name=include/fossil-scm/cli.h)</tt> for a mini-framework to bootstrap new apps and [f-apps][].
<h2>News</h2>
Notable changes (newest at the top)...
* 20130919: Realized i hadn't updated the news in a while. Future news will be posted as [technotes in the /timeline](/timeline?y=e).
|