1
1
Граф коммитов

10 Коммитов

Автор SHA1 Сообщение Дата
MPI Team
43c40b6b8a Update git/hg ignore files
This commit was SVN r31713.
2014-05-10 05:00:26 +00:00
MPI Team
a7505bcaad Update git/hg ignore files
This commit was SVN r31681.
2014-05-08 05:00:38 +00:00
MPI Team
ac5f224d68 Update git/hg ignore files
This commit was SVN r31643.
2014-05-06 05:00:35 +00:00
MPI Team
268c454bb2 Update git/hg ignore files
This commit was SVN r31597.
2014-05-02 05:00:31 +00:00
MPI Team
71f2407929 Update git/hg ignore files
This commit was SVN r31581.
2014-05-01 05:00:32 +00:00
MPI Team
4369206f2c Update git/hg ignore files
This commit was SVN r31563.
2014-04-30 05:00:33 +00:00
MPI Team
ff7814cdd0 Update git/hg ignore files
This commit was SVN r31541.
2014-04-29 05:00:26 +00:00
MPI Team
108469a2c5 Update git/hg ignore files
This commit was SVN r31531.
2014-04-26 05:00:26 +00:00
MPI Team
79fc284701 Update git/hg ignore files
This commit was SVN r31462.
2014-04-20 05:00:33 +00:00
MPI Team
5e4371139d 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-15 22:24:44 +00:00