ports/openmpi
ports/openmpi
1
1
Форкнуть 0
Код Релизы Активность
2333f8249f
openmpi/.gitignore

618 строки
15 KiB
Plaintext
Исходник Обычный вид История

Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
.libs
.deps
.libs
gitignore: a few more consolidations
2014-12-20 04:55:29 +03:00
.dirstamp
.DS_Store
.cdt*
.project
.gdb*
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
gitignore: a few more consolidations
2014-12-20 04:55:29 +03:00
.hgrc
.hgignore
.hg
.hgignore_local
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
*.la
*.lo
*.o
*.so
*.a
Add *.dwarf to the ignores as Mac Yosemite now generates these files
2014-11-18 19:47:20 +03:00
*.dwarf
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
*.dSYM
*.S
*.loT
*.orig
*.rej
gitignore: trim a lot of kruft This gitignore was simply the catenation of all the svn:ignore properties. However, .gitignore is pretty good at regular expressions that span the entire tree, so we can consolidate/remove a lot of redundant entries.
2014-12-20 04:33:51 +03:00
*.bak
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
*.class
*.xcscheme
Ignore *.out files generated by making tarballs
2014-11-19 23:31:07 +03:00
*.out
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
*.plist
gitignore: trim a lot of kruft This gitignore was simply the catenation of all the svn:ignore properties. However, .gitignore is pretty good at regular expressions that span the entire tree, so we can consolidate/remove a lot of redundant entries.
2014-12-20 04:33:51 +03:00
*.orig
*.obj
*.mod
*.i90
*.ii
*.ti
gitignore: a few more consolidations
2014-12-20 04:55:29 +03:00
*.exe
*.log
*.trs
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
*~
gitignore: a few more consolidations
2014-12-20 04:55:29 +03:00
*\\#
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
Makefile
Makefile.in
static-components.h
*\\#
config.cache
aclocal.m4
autom4te.cache
config.log
config.status
configure
libtool
doxygen
bin
lib
cscope.*
etags
GRTAGS
GSYMS
GTAGS
GPATH
vc70.pdb
.hgrc
.hgignore
.hg
.hgignore_local
gitignore: trim a lot of kruft This gitignore was simply the catenation of all the svn:ignore properties. However, .gitignore is pretty good at regular expressions that span the entire tree, so we can consolidate/remove a lot of redundant entries.
2014-12-20 04:33:51 +03:00
stamp-h?
ar-lib
ylwrap
Update .gitignore This commit was SVN r31024.
2014-03-12 17:20:50 +04:00
config.lt
gitignore: trim a lot of kruft This gitignore was simply the catenation of all the svn:ignore properties. However, .gitignore is pretty good at regular expressions that span the entire tree, so we can consolidate/remove a lot of redundant entries.
2014-12-20 04:33:51 +03:00
config.guess
config.sub
depcomp
compile
install-sh
ltmain.sh
missing
mkinstalldirs
libtool.m4
lt~obsolete.m4
ltdl.m4
argz.m4
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
ltargz.m4
gitignore: trim a lot of kruft This gitignore was simply the catenation of all the svn:ignore properties. However, .gitignore is pretty good at regular expressions that span the entire tree, so we can consolidate/remove a lot of redundant entries.
2014-12-20 04:33:51 +03:00
ltsugar.m4
ltversion.m4
ltoptions.m4
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
config/project_list.m4
config/autogen_found_items.m4
config/opal_get_version.sh
config/test-driver
gitignore: trim a lot of kruft This gitignore was simply the catenation of all the svn:ignore properties. However, .gitignore is pretty good at regular expressions that span the entire tree, so we can consolidate/remove a lot of redundant entries.
2014-12-20 04:33:51 +03:00
config/mca_no_configure_components.m4
config/mca_m4_config_include.m4
config/ext_no_configure_components.m4
config/ext_m4_config_include.m4
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
contrib/build-mca-comps-outside-of-tree/btl_tcp2_config.h
contrib/build-mca-comps-outside-of-tree/btl_tcp2_config.h.in
contrib/build-mca-comps-outside-of-tree/config
contrib/build-mca-comps-outside-of-tree/aclocal.m4
contrib/dist/linux/compile_debian_mlnx_example
contrib/dist/mofed/compile_debian_mlnx_example
contrib/dist/mofed/debian/changelog
contrib/dist/mofed/debian/control
contrib/dist/mofed/debian/copyright
contrib/dist/mofed/debian/rules
contrib/platform/intel/bend/*orcm*
contrib/scaling/orte_no_op
contrib/scaling/mpi_no_op
contrib/scaling/mpi_barrier
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
examples/hello_c
examples/hello_cxx
examples/hello_mpifh
examples/hello_usempi
examples/hello_usempif08
examples/ring_c
examples/ring_cxx
examples/ring_mpifh
examples/ring_usempi
examples/ring_usempif08
examples/connectivity_c
Update .gitignore This commit was SVN r31024.
2014-03-12 17:20:50 +04:00
examples/ring_oshmem
examples/hello_oshmem
examples/ring_oshmemfh
examples/hello_oshmemfh
Update git/hg ignore files This commit was SVN r31875.
2014-05-22 09:00:26 +04:00
examples/oshmem_circular_shift
examples/oshmem_max_reduction
examples/oshmem_shmalloc
examples/oshmem_strided_puts
examples/oshmem_symmetric_data
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/debuggers/*.in
ompi/debuggers/dlopen_test
ompi/debuggers/predefined_gap_test
Update .gitignore This commit was SVN r31024.
2014-03-12 17:20:50 +04:00
ompi/debuggers/predefined_pad_test
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/include/mpi.h
ompi/include/mpif-config.h
ompi/include/mpif.h
fortran: fix f08 bindings only define the unique fortran symbol depending on - CAPS - PLAIN - SINGLE_UNDERSCORE - DOUBLE_UNDERSCORE and bind the f08 symbol to the uniquely defined C symbol. Use real data structures to make the code simpler. (perl script written by Jeff)
2015-07-24 03:51:21 +03:00
ompi/include/mpif-c-constants-decl.h
ompi/include/mpif-c-constants.h
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/include/mpif-common.h
ompi/include/mpi-ext.h
ompi/include/mpif-ext.h
fortran: fix f08 bindings only define the unique fortran symbol depending on - CAPS - PLAIN - SINGLE_UNDERSCORE - DOUBLE_UNDERSCORE and bind the f08 symbol to the uniquely defined C symbol. Use real data structures to make the code simpler. (perl script written by Jeff)
2015-07-24 03:51:21 +03:00
ompi/include/mpif-f08-types.h
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/include/mpif-handles.h
ompi/include/mpif-io-constants.h
ompi/include/mpif-constants.h
ompi/include/mpif-io-handles.h
Update git/hg ignore files This commit was SVN r32768.
2014-09-20 09:00:28 +04:00
ompi/include/mpif-sizeof.h
Update .gitignore This commit was SVN r31024.
2014-03-12 17:20:50 +04:00
ompi/include/mpi_portable_platform.h
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/include/ompi/version.h
ompi/include/ompi/frameworks.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mca/coll/basic/coll-basic-version.h*
ompi/mca/coll/demo/config
ompi/mca/coll/demo/coll_demo_config.h*
ompi/mca/coll/demo/coll-demo-version.h*
ompi/mca/coll/ml/coll_ml_lex.c
ompi/mca/coll/self/coll-self-version.h*
ompi/mca/coll/sm/coll-sm-version.h*
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mca/crcp/ompi_crcp.7
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
.gitignore: update for ROMIO refresh
2015-05-02 13:27:18 +03:00
ompi/mca/io/romio314/romio/adio/include/romioconf.h
ompi/mca/io/romio314/romio/include/mpio.h
ompi/mca/io/romio314/romio/localdefs
ompi/mca/io/romio314/romio/test/fcoll_test.f
ompi/mca/io/romio314/romio/test/fmisc.f
ompi/mca/io/romio314/romio/test/fperf.f
ompi/mca/io/romio314/romio/test/large_file.c
ompi/mca/io/romio314/romio/test/misc.c
ompi/mca/io/romio314/romio/test/pfcoll_test.f
ompi/mca/io/romio314/romio/test/runtests
ompi/mca/io/romio314/romio/util/romioinstall
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mca/pml/v/autogen.vprotocols
ompi/mca/pml/v/mca_vprotocol_config_output
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/mca/rte/orte/ompi-ps.1
ompi/mca/rte/orte/ompi-clean.1
ompi/mca/rte/orte/mpiexec.1
ompi/mca/rte/orte/ompi-top.1
ompi/mca/rte/orte/ompi-server.1
Update .gitignore This commit was SVN r31024.
2014-03-12 17:20:50 +04:00
ompi/mca/rte/orte/ompi-restart.1
ompi/mca/rte/orte/ompi-checkpoint.1
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/mca/rte/orte/mpirun.1
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/mca/sharedfp/addproc/mca_sharedfp_addproc_control
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/c/profile/p*.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/fortran/configure-fortran-output.h
ompi/mpi/fortran/mpiext/mpi-ext-module.F90
ompi/mpi/fortran/mpiext/mpi-f08-ext-module.F90
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update git/hg ignore files This commit was SVN r32768.
2014-09-20 09:00:28 +04:00
ompi/mpi/fortran/mpif-h/sizeof_f.f90
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/fortran/mpif-h/profile/p*.c
Update git/hg ignore files This commit was SVN r32768.
2014-09-20 09:00:28 +04:00
ompi/mpi/fortran/mpif-h/profile/psizeof_f.f90
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/fortran/use-mpi-f08/constants.h
Update git/hg ignore files This commit was SVN r32768.
2014-09-20 09:00:28 +04:00
ompi/mpi/fortran/use-mpi-f08/sizeof_f08.f90
ompi/mpi/fortran/use-mpi-f08/sizeof_f08.h
ompi/mpi/fortran/use-mpi-f08/profile/psizeof_f08.f90
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/fortran/use-mpi-ignore-tkr/mpi-ignore-tkr-interfaces.h
ompi/mpi/fortran/use-mpi-ignore-tkr/mpi-ignore-tkr-file-interfaces.h
Update git/hg ignore files This commit was SVN r32768.
2014-09-20 09:00:28 +04:00
ompi/mpi/fortran/use-mpi-ignore-tkr/mpi-ignore-tkr-sizeof.f90
ompi/mpi/fortran/use-mpi-ignore-tkr/mpi-ignore-tkr-sizeof.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/fortran/use-mpi-tkr/fortran_kinds.sh
ompi/mpi/fortran/use-mpi-tkr/fortran_sizes.h
ompi/mpi/fortran/use-mpi-tkr/mpi_kinds.ompi_module
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/java/java/mpi
ompi/mpi/java/java/*.jar
ompi/mpi/java/java/*.h
ompi/mpi/java/java/doc
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/man/man3/MPI*.3
ompi/mpi/man/man3/OpenMPI.3
ompi/mpi/man/man3/.dir-stamp
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/tool/profile/*.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpiext/affinity/c/OMPI_Affinity_str.3
ompi/mpiext/affinity/c/example
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpiext/example/tests/progress_c
ompi/mpiext/example/tests/progress_mpifh
ompi/mpiext/example/tests/progress_usempi
ompi/mpiext/example/tests/progress_usempif08
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
.gitignore: add man page in CUDA extension
2015-08-06 16:49:33 +03:00
ompi/mpiext/cuda/c/MPIX_Query_cuda_support.3
Update ignores
2015-08-15 17:56:31 +03:00
ompi/mpiext/cuda/c/mpiext_cuda_c.h
.gitignore: add man page in CUDA extension
2015-08-06 16:49:33 +03:00
Update git/hg ignore files This commit was SVN r32739.
2014-09-16 09:00:23 +04:00
ompi/tools/mpisync/mpisync
ompi/tools/mpisync/mpirun_prof
ompi/tools/mpisync/ompi_timing_post
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/tools/ompi_info/ompi_info
ompi/tools/ompi_info/ompi_info.1
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/tools/wrappers/mpic++-wrapper-data.txt
ompi/tools/wrappers/mpicc-wrapper-data.txt
ompi/tools/wrappers/mpifort-wrapper-data.txt
ompi/tools/wrappers/mpicc.1
ompi/tools/wrappers/mpic++.1
ompi/tools/wrappers/mpicxx.1
ompi/tools/wrappers/mpifort.1
ompi/tools/wrappers/ompi_wrapper_script
ompi/tools/wrappers/ompi.pc
ompi/tools/wrappers/ompi-c.pc
ompi/tools/wrappers/ompi-cxx.pc
ompi/tools/wrappers/ompi-fort.pc
ompi/tools/wrappers/mpijavac.pl
ompi/tools/wrappers/mpif90.1
ompi/tools/wrappers/mpif77.1
ompi/tools/wrappers/mpicxx-wrapper-data.txt
ompi/tools/wrappers/mpif77-wrapper-data.txt
ompi/tools/wrappers/mpif90-wrapper-data.txt
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/libltdl
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/asm/atomic-asm.S
opal/asm/atomic-test
opal/asm/generated/atomic-*.s
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/include/opal_config.h
opal/include/opal_config.h.in
opal/include/opal/install_dirs.h
opal/include/opal/version.h
opal/include/opal/frameworks.h
opal/include/opal/sys/powerpc/atomic-32.s
opal/include/opal/sys/powerpc/atomic-64.s
opal/include/opal/sys/powerpc/atomic-32-64.s
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/mca/base/mca_base_parse_paramfile_lex.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
libfabric configury: make AC_CONFIG_FILES be unconditional Also add the generated config.h file to .gitignore.
2014-12-20 19:30:32 +03:00
opal/mca/common/libfabric/libfabric/config.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update git/hg ignore files This commit was SVN r32320.
2014-07-26 09:00:28 +04:00
opal/mca/btl/openib/btl_openib_lex.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
.gitignore: ignore usnic unit test executable
2014-12-04 01:20:33 +03:00
opal/mca/btl/usnic/usnic_btl_run_tests
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/mca/crs/opal_crs.7
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
gitignore: even more regexp ignores Simple regexps to always ignore the hwloc/libevent stuff, regardless of their specific version. Yay regexps!
2014-12-20 04:44:26 +03:00
opal/mca/event/libevent*/libevent/config.h.in
opal/mca/event/libevent*/libevent/config.h
opal/mca/event/libevent*/libevent/libevent.pc
opal/mca/event/libevent*/libevent/libevent_openssl.pc
opal/mca/event/libevent*/libevent/libevent_pthreads.pc
opal/mca/event/libevent*/libevent/include/event2/event-config.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
gitignore: even more regexp ignores Simple regexps to always ignore the hwloc/libevent stuff, regardless of their specific version. Yay regexps!
2014-12-20 04:44:26 +03:00
opal/mca/hwloc/hwloc*/hwloc/include/hwloc/autogen/config.h
opal/mca/hwloc/hwloc*/hwloc/include/private/autogen/config.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/mca/installdirs/config/install_dirs.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Integrate PMIx 1.0 with OMPI. Bring Slurm PMI-1 component online Bring the s2 component online Little cleanup - let the various PMIx modules set the process name during init, and then just raise it up to the ORTE level. Required as the different PMI environments all pass the jobid in different ways. Bring the OMPI pubsub/pmi component online Get comm_spawn working again Ensure we always provide a cpuset, even if it is NULL pmix/cray: adjust cray pmix component for pmix Make changes so cray pmix can work within the integrated ompi/pmix framework. Bring singletons back online. Implement the comm_spawn operation using pmix - not tested yet Cleanup comm_spawn - procs now starting, error in connect_accept Complete integration
2015-06-18 19:53:20 +03:00
opal/mca/pmix/pmix1xx/pmix/include/pmix/autogen/config.h
opal/mca/pmix/pmix1xx/pmix/include/pmix/pmix_common.h
opal/mca/pmix/pmix1xx/pmix/include/private/autogen/config.h
opal/mca/pmix/pmix1xx/pmix/include/private/autogen/config.h.in
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/tools/opal-checkpoint/opal-checkpoint
opal/tools/opal-checkpoint/opal-checkpoint.1
opal/tools/opal-restart/opal-restart
opal/tools/opal-restart/opal-restart.1
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/tools/wrappers/opalcc-wrapper-data.txt
opal/tools/wrappers/opalc++-wrapper-data.txt
opal/tools/wrappers/opalCC-wrapper-data.txt
opal/tools/wrappers/opal_wrapper
opal/tools/wrappers/opalcc.1
opal/tools/wrappers/opalc++.1
opal/tools/wrappers/generic_wrapper.1
opal/tools/wrappers/opal_wrapper.1
opal/tools/wrappers/opal.pc
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/util/show_help_lex.c
opal/util/keyval/keyval_lex.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
orte/doxygen
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
orte/include/orte/version.h
orte/include/orte/frameworks.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
orte/mca/filem/orte_filem.7
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
orte/mca/rmaps/rank_file/rmaps_rank_file_lex.c
orte/mca/rmaps/rank_file/rankfile_lex.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
orte/mca/snapc/orte_snapc.7
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
orte/mca/sstore/orte_sstore.7
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
orte/test/mpi/abort
orte/test/mpi/accept
orte/test/mpi/bad_exit
orte/test/mpi/bcast_loop
orte/test/mpi/concurrent_spawn
orte/test/mpi/connect
orte/test/mpi/crisscross
orte/test/mpi/delayed_abort
orte/test/mpi/hello_barrier
orte/test/mpi/hello_nodename
orte/test/mpi/hello_output
orte/test/mpi/hello_show_help
orte/test/mpi/hello
orte/test/mpi/hello++
orte/test/mpi/loop_child
orte/test/mpi/loop_spawn
orte/test/mpi/mpi_barrier
orte/test/mpi/mpi_no_op
orte/test/mpi/mpi_spin
orte/test/mpi/multi_abort
orte/test/mpi/parallel_r8
orte/test/mpi/parallel_r64
orte/test/mpi/parallel_w8
orte/test/mpi/parallel_w64
orte/test/mpi/pubsub
orte/test/mpi/read_write
orte/test/mpi/reduce-hang
orte/test/mpi/segv
orte/test/mpi/simple_spawn
orte/test/mpi/slave
orte/test/mpi/spawn_multiple
orte/test/mpi/ziaprobe
orte/test/mpi/ziatest
Update git/hg ignore files This commit was SVN r32235.
2014-07-15 09:00:26 +04:00
orte/test/mpi/*.dwarf
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
orte/test/mpi/junk*
orte/test/mpi/sio
orte/test/mpi/sendrecv_blaster
orte/test/mpi/early_abort
orte/test/mpi/spawn_problem/ch_rec
orte/test/mpi/spawn_problem/output
orte/test/mpi/spawn_problem/start
orte/test/mpi/debugger
orte/test/mpi/server_port_name.txt
orte/test/mpi/singleton_client_server
orte/test/mpi/intercomm_create
orte/test/mpi/spawn_tree
orte/test/mpi/init-exit77
orte/test/mpi/mpi_info
orte/test/mpi/info_spawn
orte/test/mpi/client
orte/test/mpi/server
orte/test/mpi/paccept
orte/test/mpi/pconnect
orte/test/mpi/thread_init
orte/test/mpi/memcached-dummy
Update git/hg ignore files This commit was SVN r32214.
2014-07-11 09:00:25 +04:00
orte/test/mpi/coll_test
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
orte/test/system/radix
orte/test/system/sigusr_trap
orte/test/system/orte_no_op
orte/test/system/no_op
orte/test/system/hello
orte/test/system/hello_nodename
orte/test/system/hello_null
orte/test/system/spin
orte/test/system/orte_nodename
orte/test/system/orte_proc_subscribe
orte/test/system/orte_spawn
orte/test/system/orte_stage_gate
orte/test/system/orte_loop_spawn
orte/test/system/orte_loop_child
orte/test/system/orte_abort
orte/test/system/get_limits
orte/test/system/orte_ring
orte/test/system/spawn_child
orte/test/system/orte_tool
orte/test/system/binom
orte/test/system/iof_stress
orte/test/system/oob_stress
orte/test/system/iof_delay
orte/test/system/orte_barrier
orte/test/system/orte_mcast
orte/test/system/mcast
orte/test/system/mcast_recv
orte/test/system/opal_interface
orte/test/system/orte_spin
orte/test/system/segfault
orte/test/system/sysinfo
orte/test/system/orte_exit
orte/test/system/orte_db
orte/test/system/orte_state
orte/test/system/orte_sensor
orte/test/system/event-threads
orte/test/system/test-time
orte/test/system/psm_keygen
orte/test/system/regex
orte/test/system/orte_errors
orte/test/system/evthread-test
orte/test/system/evpri-test
orte/test/system/opal-evpri-test
orte/test/system/evpri-test2
orte/test/system/mapper
orte/test/system/reducer
orte/test/system/opal_hotel
orte/test/system/orte_dfs
orte/test/system/orte_allocate
orte/test/system/getenv_pmi
orte/test/system/pmi_abort
orte/test/system/opal_hwloc
orte/test/system/opal_db
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
orte/tools/orte-checkpoint/orte-checkpoint
orte/tools/orte-checkpoint/orte-checkpoint.1
orte/tools/orte-checkpoint/ompi-checkpoint.1
orte/tools/orte-clean/orte-clean
orte/tools/orte-clean/orte-clean.1
Enable persistent ORTE DVM so users can execute multiple OMPI jobs within an allocation without restarting the DVM every time.
2015-01-30 22:00:43 +03:00
orte/tools/orte-dvm/orte-dvm
orte/tools/orte-dvm/orte-dvm.1
Update orte-submit manpage, add the ompi-* versions of orte-dvm and orte-submit manpages
2015-02-02 02:46:40 +03:00
ompi/mca/rte/orte/ompi-dvm.1
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
orte/tools/orte-info/orte-info
orte/tools/orte-info/orte-info.1
orte/tools/orte-migrate/orte-migrate
orte/tools/orte-migrate/orte-migrate.1
orte/tools/orte-migrate/ompi-migrate.1
orte/tools/orte-ps/orte-ps
orte/tools/orte-ps/orte-ps.1
orte/tools/orte-restart/orte-restart
orte/tools/orte-restart/orte-restart.1
orte/tools/orte-restart/ompi-restart.1
orte/tools/orte-server/orte-server
orte/tools/orte-server/orte-server.1
Enable persistent ORTE DVM so users can execute multiple OMPI jobs within an allocation without restarting the DVM every time.
2015-01-30 22:00:43 +03:00
orte/tools/orte-submit/orte-submit
orte/tools/orte-submit/orte-submit.1
Update orte-submit manpage, add the ompi-* versions of orte-dvm and orte-submit manpages
2015-02-02 02:46:40 +03:00
ompi/mca/rte/orte/ompi-submit.1
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
orte/tools/orte-top/orte-top
orte/tools/orte-top/orte-top.1
orte/tools/orted/orted
orte/tools/orted/orted.1
orte/tools/orterun/orterun
orte/tools/orterun/orterun.1
orte/tools/wrappers/ortecc-wrapper-data.txt
orte/tools/wrappers/ortec++-wrapper-data.txt
orte/tools/wrappers/ortecc.1
orte/tools/wrappers/ortec++.1
orte/tools/wrappers/orte_wrapper_script
orte/tools/wrappers/orte.pc
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
orte/util/hostfile/hostfile_lex.c
orte/util/hostfile/orte_hosts.7
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
oshmem/include/shmem.h
oshmem/include/shmem_portable_platform.h
oshmem/include/oshmem/frameworks.h
oshmem/include/oshmem/version.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
oshmem/mca/sshmem/base/static-components.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
oshmem/shmem/c/profile/p*.c
oshmem/shmem/c/profile/*.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
oshmem/shmem/fortran/libshmem_fortran.la
Update git/hg ignore files This commit was SVN r31563.
2014-04-30 09:00:33 +04:00
oshmem/shmem/fortran/profile/pshmem_*_f.c
Update git/hg ignore files This commit was SVN r31581.
2014-05-01 09:00:32 +04:00
oshmem/shmem/fortran/profile/pshpdeallc_f.c
oshmem/shmem/fortran/profile/pshpclmove_f.c
oshmem/shmem/fortran/profile/pmy_pe_f.c
oshmem/shmem/fortran/profile/pshpalloc_f.c
oshmem/shmem/fortran/profile/pnum_pes_f.c
oshmem/shmem/fortran/profile/pstart_pes_f.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update git/hg ignore files This commit was SVN r31813.
2014-05-19 09:00:28 +04:00
oshmem/shmem/java/java/shmem.jar
oshmem/shmem/java/java/doc
oshmem/shmem/java/java/shmem_Constant.h
oshmem/shmem/java/java/shmem_ShMem.h
oshmem/shmem/java/java/shmem
oshmem/shmem/java/java/shmem_Addr.h
Update git/hg ignore files This commit was SVN r31925.
2014-06-02 09:00:30 +04:00
oshmem/shmem/java/java/shmem_PSync.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
oshmem: Add man related files into gitignore Signed-off-by: Igor Ivanov <Igor.Ivanov@itseez.com>
2015-08-25 13:04:44 +03:00
oshmem/shmem/man/man3/shmem_*.3
oshmem/shmem/man/man3/OpenSHMEM.3
oshmem/shmem/man/man3/intro_shmem.3
oshmem/shmem/man/man3/_my_pe.3
oshmem/shmem/man/man3/_num_pes.3
oshmem/shmem/man/man3/shfree.3
oshmem/shmem/man/man3/shmalloc.3
oshmem/shmem/man/man3/shmemalign.3
oshmem/shmem/man/man3/shrealloc.3
oshmem/shmem/man/man3/start_pes.3
oshmem/shmem/man/man3/.dir-stamp
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
oshmem/tools/oshmem_info/oshmem_info
oshmem/tools/oshmem_info/oshmem_info.1
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
oshmem/tools/wrappers/shmemcc-wrapper-data.txt
oshmem/tools/wrappers/shmemfort-wrapper-data.txt
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/asm/atomic_math_noinline
test/asm/atomic_barrier
test/asm/atomic_cmpset_noinline
test/asm/atomic_math
test/asm/atomic_cmpset
test/asm/atomic_spinlock_noinline.c
test/asm/atomic_barrier_noinline.c
test/asm/atomic_math_noinline.c
test/asm/atomic_cmpset_noinline.c
test/asm/atomic_spinlock_noinline
test/asm/atomic_barrier_noinline
test/asm/atomic_spinlock
.gitignore: add a missing test executable Also alphebetize the ignored files in test/class.
2014-12-01 21:56:11 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/class/*.txt
test/class/ompi_bitmap_test_out.txt
.gitignore: add a missing test executable Also alphebetize the ignored files in test/class.
2014-12-01 21:56:11 +03:00
test/class/ompi_circular_buffer_fifo
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/class/ompi_fifo
test/class/ompi_rb_tree
test/class/ompi_bitmap
test/class/opal_bitmap
.gitignore: ignore executes for new tests
2014-12-11 21:02:10 +03:00
test/class/opal_fifo
.gitignore: add a missing test executable Also alphebetize the ignored files in test/class.
2014-12-01 21:56:11 +03:00
test/class/opal_hash_table
.gitignore: ignore executes for new tests
2014-12-11 21:02:10 +03:00
test/class/opal_lifo
.gitignore: add a missing test executable Also alphebetize the ignored files in test/class.
2014-12-01 21:56:11 +03:00
test/class/opal_list
test/class/opal_pointer_array
test/class/opal_proc_table
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/class/opal_tree
.gitignore: add a missing test executable Also alphebetize the ignored files in test/class.
2014-12-01 21:56:11 +03:00
test/class/opal_value_array
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/datatype/ddt_test
test/datatype/ddt_pack
test/datatype/to_self
test/datatype/checksum
test/datatype/position
test/datatype/ddt_raw
test/datatype/opal_datatype_test
.gitignore: add more test executables to be ignored
2014-11-22 02:08:36 +03:00
test/datatype/position_noncontig
test/datatype/unpack_ooo
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/dss/dss_buffer
test/dss/dss_copy
test/dss/dss_size
test/dss/dss_cmp
test/dss/dss_release
test/dss/dss_payload
test/dss/dss_set_get
test/dss/dss_print
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/event/signal-test
test/event/event-test
test/event/time-test
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/mpi/environment/chello
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/runtime/parse_context
test/runtime/sigchld
test/runtime/start_shut
test/runtime/opal_init_finalize
test/runtime/orte_init_finalize
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/threads/opal_condition
test/threads/opal_thread
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/util/aaa
test/util/test_session_dir_out
test/util/opal_os_path
test/util/opal_argv
test/util/opal_os_create_dirpath
test/util/opal_if
test/util/opal_error
test/util/opal_timer
test/util/orte_sys_info
test/util/orte_session_dir
test/util/orte_sys_info
test/util/orte_universe_setup_file_io
test/util/opal_basename
test/util/ompi_numtostr
test/util/ompi_pack
test/util/test-file
test/util/opal_sos
test/util/opal_path_nfs
test/util/opal_path_nfs.out
test/util/opal_bit_ops
Копировать постоянную ссылку