Mercurial > octave-nkf
view .hgignore @ 17791:224e76250443
Use GNU style coding conventions for code in examples/
* examples/embedded.cc, examples/fortdemo.cc, examples/helloworld.cc,
examples/make_int.cc, examples/mycell.c, examples/myfeval.c, examples/myfunc.c,
examples/mypow2.c, examples/myprop.c, examples/myset.c, examples/mystring.c,
examples/mystruct.c, examples/oct_demo.cc, examples/oregonator.cc:
Use GNU style coding conventions for code in examples/
author | Rik <rik@octave.org> |
---|---|
date | Tue, 29 Oct 2013 10:28:39 -0700 |
parents | dc76e3909d36 |
children | c16c446204e5 |
line wrap: on
line source
syntax: regexp # The recurrent (^|/) idiom in the regexps below should be understood # to mean "at any directory" while the ^ idiom means "from the # project's top-level directory". # gnulib makes these silly backup files .~$ # This directory gets created by gnulib during the build. # It contains no Octave files. ^libgnu/* # This directory mostly contains cruft during build time, but it does # contain some Octave code, so we gotta be a bit more careful about # what we ignore here ^m4/(?!ax_).+\.m4$ # Emacs tools create these (^|/)TAGS$ (^|/)semantic.cache$ (/|^)Makefile\.in$ ^INSTALL$ ^aclocal\.m4$ ^build-.*($|/) ^configure$ ^autom4te\.cache($|/) ^config\.in\.h$ # e.g. doc/faq/OctaveFAQ.info # doc/interpreter/octave.info-4 ^doc/.*\.info(-\d)?$ ^doc/\w*/stamp-vti$ ^doc/\w*/version\.texi$ ^doc/interpreter/images\.mk$ # e.g. liboctave/operators/smx-op-inc.mk ^liboctave/operators/\w+-op-\w+\.mk$ ^libinterp/dldfcn/module\.mk$