view .hgignore @ 20265:e914b5399c67

Use in-place operators in C++ code where possible. * libgui/src/dialog.cc, libgui/src/m-editor/file-editor-tab.cc, libgui/src/main-window.cc, libinterp/corefcn/bsxfun.cc, libinterp/corefcn/filter.cc, libinterp/corefcn/mgorth.cc, libinterp/corefcn/oct-stream.cc, libinterp/corefcn/pr-output.cc, liboctave/array/Array-util.cc, liboctave/array/dim-vector.h, liboctave/numeric/CollocWt.cc, liboctave/numeric/eigs-base.cc, liboctave/numeric/lo-specfun.cc: Use in-place operators in C++ code where possible.
author Rik <rik@octave.org>
date Mon, 25 May 2015 22:02:15 -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$