My patches to CMake
Go to file
Brad King 7e293acce3 Exclude from source archives files specific to Git work tree
Add the "export-ignore" attribute to all such files.  Remove the
suggestion from the README since this should not be a responsibility
of the including project.
2012-03-02 13:39:29 -05:00
.gitattributes Exclude from source archives files specific to Git work tree 2012-03-02 13:39:29 -05:00
LICENSE Add LICENSE and NOTICE 2012-02-08 14:26:31 -05:00
NOTICE Add LICENSE and NOTICE 2012-02-08 14:26:31 -05:00
README Exclude from source archives files specific to Git work tree 2012-03-02 13:39:29 -05:00
config.sample Add README instructions and sample configuration 2012-02-09 10:54:32 -05:00
setup-gerrit Add 'setup-gerrit' script to configure Gerrit access 2012-02-09 10:44:43 -05:00
setup-hooks Add 'setup-hooks' script to install local hooks 2012-02-09 10:44:43 -05:00
setup-ssh Add 'setup-ssh' script to configure ssh push access 2012-02-09 10:44:43 -05:00
setup-stage Add 'setup-stage' script to configure topic stage remote 2012-02-09 10:44:43 -05:00
setup-user Add 'setup-user' script to configure authorship information 2012-02-09 10:44:40 -05:00
tips Add 'tips' script to suggest local configuration 2012-02-09 10:44:15 -05:00

README

Kitware Local Git Setup Scripts


Introduction
------------

This is a collection of local Git development setup scripts meant for
inclusion in project source trees to aid their development workflow.
Project-specific information needed by the scripts may be configured
in a "config" file added next to them in the project.


Import
------

A project may import these scripts into their source tree by
initializing a subtree merge.  Bring up a Git prompt and set the
current working directory inside a clone of the target project.
Fetch the "setup" branch from the GitSetup repository:

 $ git fetch ../GitSetup setup:setup

Prepare to merge the branch but place the content in a subdirectory.
Any prefix (with trailing '/') may be chosen so long as it is used
consistently within a project through the rest of these instructions:

 $ git merge -s ours --no-commit setup
 $ git read-tree -u --prefix=Utilities/GitSetup/ setup

Commit the merge with an informative message:

 $ git commit
 ------------------------------------------------------------------------
 Merge branch 'setup'

 Add Utilities/GitSetup/ directory using subtree merge from
 the general GitSetup repository "setup" branch.
 ------------------------------------------------------------------------


Configuration
-------------

Read the "Project configuration instructions" comment in each script.
Add a "config" file next to the scripts with desired configuration
(optionally copy and modify "config.sample").  For example, to
configure the "setup-hooks" script:

 $ git config -f Utilities/GitSetup/config hooks.url "$url"

where "$url" is the project repository publishing the "hooks" branch.
When finished, add and commit the configuration file:

 $ git add Utilities/GitSetup/config
 $ git commit


Update
------

A project may update these scripts from the GitSetup repository.
Bring up a Git prompt and set the current working directory inside a
clone of the target project.  Fetch the "setup" branch from the
GitSetup repository:

 $ git fetch ../GitSetup setup:setup

Merge the "setup" branch into the subtree:

 $ git merge -X subtree=Utilities/GitSetup setup

where "Utilities/GitSetup" is the same prefix used during the import
setup, but without a trailing '/'.


License
-------

Distributed under the Apache License 2.0.
See LICENSE and NOTICE for details.