First Commit

.gitignore

@@ -0,0 +1,64 @@
+Makefile
+*.log
+*.swp
+/*.tar.bz2
+/*.tar.gz
+/*.tar.xz
+*.la
+*.lo
+*.o
+*~
+Makefile.in
+aclocal.m4
+config.*
+configure
+autom4te.cache
+compile
+install-sh
+missing
+ltmain.sh
+depcomp
+stamp-*
+libtool
+tap-driver.sh
+test-driver
+.deps
+.libs
+build-aux/m4/libtool.m4
+build-aux/m4/lt~obsolete.m4
+build-aux/m4/ltoptions.m4
+build-aux/m4/ltsugar.m4
+build-aux/m4/ltversion.m4
+.dirstamp
+*.trs
+/cscope.*
+/tags
+telemd
+autoscan.log
+configure.scan
+tprobe
+hprobe
+crashprobe
+journalprobe
+telem-record-gen
+klogscanner
+oopsprobe
+pstoreclean
+pstoreprobe
+make.out
+types_c.taghl
+src/recomp.sh
+src/*.so
+src/gcc.out
+tests/demo
+tests/check_config
+tests/check_daemon
+tests/check_libtelemetry
+tests/check_probes
+src/data/*.path
+src/data/*.service
+src/data/*.socket
+src/data/telemetrics.conf
+src/data/telemetrics-dirs.conf
+src/data/libtelemetry.pc
+src/data/40-crash-probe.conf

AUTHORS

@@ -0,0 +1,5 @@
+Archana Shinde <[email protected]>
+Patrick McCarty <[email protected]>
+Rob Nesius <[email protected]>
+Gabrielle N. Beyer <[email protected]>
+Pam Leonard <[email protected]>

CODING-STYLE

@@ -0,0 +1,78 @@
+Indentation
+-----------
+telemetrics-client uses spaces for indentation (no tabs). To help enforce this
+rule, all source files provide modelines; if your editor does not support
+modelines, configure your editor accordingly.
+
+Line length
+-----------
+Wherever possible, try to limit line length to 80 characters.
+
+Coding Style
+------------
+- Function declarations and invocations should include no space between the
+  function name and the open parenthesis:
+
+        spool_max_size_config();
+
+- All other usages of parentheses in code should have one intervening space:
+
+        if (spool_size == -1) {
+                ...
+        }
+
+- To distinguish function definitions from other top-level constructs, add the
+  opening curly bracket on its own line:
+
+        void spool_record(char *headers[], char *body)
+        {
+                ...
+        }
+
+- All other usages of curly brackets in code should include the opening curly
+  bracket at the end of the line which opens the block:
+
+        for (i = 0; i < NUM_HEADERS; i++) {
+                ...
+        }
+
+- if statements should *always* use curly brackets, even when each clause only
+  contains a single statement. This is a safeguard to ensure future changes to
+  an if statement are not buggy due to forgetting to add the curly brackets
+  when needed.
+
+        if (ret == -1) {
+                ...
+        }
+
+- Comments that span more than one line should use the following style:
+
+        /* This comment
+         * spans more
+         * than one
+         * line.
+         */
+
+- For single-line comments, use either of the following forms:
+
+        /* single line comment 1 */
+
+        // single line comment 2
+
+- To make type casts stand out more, include no space between the cast and the
+  variable, etc. to cast:
+
+        GString **foo = (GString **)bar;
+
+- Whenever arithmetic operators are used, always include one space before and
+  after each operator:
+
+        size = size - offset + 1;
+
+- For pointer variable declarations, pointer dereferences, functions that return
+  a pointer, typecasts to a pointer variable, and other related constructs;
+  include a single space between the type and '*', and no space between the '*'
+  and the following variable, function name, etc. The purpose here is to
+  distinguish pointer usage versus arithmetic usage:
+
+        char *payload;