gitmodules - defining submodule properties




   The .gitmodules file, located in the top-level directory of a Git
   working tree, is a text file with a syntax matching the requirements of

   The file contains one subsection per submodule, and the subsection
   value is the name of the submodule. The name is set to the path where
   the submodule has been added unless it was customized with the --name
   option of git submodule add. Each submodule section also contains the
   following required keys:

       Defines the path, relative to the top-level directory of the Git
       working tree, where the submodule is expected to be checked out.
       The path name must not end with a /. All submodule paths must be
       unique within the .gitmodules file.

       Defines a URL from which the submodule repository can be cloned.
       This may be either an absolute URL ready to be passed to git-
       clone(1) or (if it begins with ./ or ../) a location relative to
       the superproject's origin repository.

   In addition, there are a number of optional keys:

       Defines the default update procedure for the named submodule, i.e.
       how the submodule is updated by "git submodule update" command in
       the superproject. This is only used by git submodule init to
       initialize the configuration variable of the same name. Allowed
       values here are checkout, rebase, merge or none. See description of
       update command in git-submodule(1) for their meaning. Note that the
       !command form is intentionally ignored here for security reasons.

       A remote branch name for tracking updates in the upstream
       submodule. If the option is not specified, it defaults to master. A
       special value of .  is used to indicate that the name of the branch
       in the submodule should be the same name as the current branch in
       the current repository. See the --remote documentation in git-
       submodule(1) for details.

       This option can be used to control recursive fetching of this
       submodule. If this option is also present in the submodules entry
       in .git/config of the superproject, the setting there will override
       the one found in .gitmodules. Both settings can be overridden on
       the command line by using the "--[no-]recurse-submodules" option to
       "git fetch" and "git pull".

       Defines under what circumstances "git status" and the diff family
       show a submodule as modified. When set to "all", it will never be
       considered modified (but will nonetheless show up in the output of
       status and commit when it has been staged), "dirty" will ignore all
       changes to the submodules work tree and takes only differences
       between the HEAD of the submodule and the commit recorded in the
       superproject into account. "untracked" will additionally let
       submodules with modified tracked files in their work tree show up.
       Using "none" (the default when this option is not set) also shows
       submodules that have untracked files in their work tree as changed.
       If this option is also present in the submodules entry in
       .git/config of the superproject, the setting there will override
       the one found in .gitmodules. Both settings can be overridden on
       the command line by using the "--ignore-submodule" option. The git
       submodule commands are not affected by this setting.

       When set to true, a clone of this submodule will be performed as a
       shallow clone unless the user explicitly asks for a non-shallow


   Consider the following .gitmodules file:

       [submodule "libfoo"]
               path = include/foo
               url = git://

       [submodule "libbar"]
               path = include/bar
               url = git://

   This defines two submodules, libfoo and libbar. These are expected to
   be checked out in the paths include/foo and include/bar, and for both
   submodules a URL is specified which can be used for cloning the


   git-submodule(1) git-config(1)


   Part of the git(1) suite


Personal Opportunity - Free software gives you access to billions of dollars of software at no cost. Use this software for your business, personal use or to develop a profitable skill. Access to source code provides access to a level of capabilities/information that companies protect though copyrights. Open source is a core component of the Internet and it is available to you. Leverage the billions of dollars in resources and capabilities to build a career, establish a business or change the world. The potential is endless for those who understand the opportunity.

Business Opportunity - Goldman Sachs, IBM and countless large corporations are leveraging open source to reduce costs, develop products and increase their bottom lines. Learn what these companies know about open source and how open source can give you the advantage.

Free Software

Free Software provides computer programs and capabilities at no cost but more importantly, it provides the freedom to run, edit, contribute to, and share the software. The importance of free software is a matter of access, not price. Software at no cost is a benefit but ownership rights to the software and source code is far more significant.

Free Office Software - The Libre Office suite provides top desktop productivity tools for free. This includes, a word processor, spreadsheet, presentation engine, drawing and flowcharting, database and math applications. Libre Office is available for Linux or Windows.

Free Books

The Free Books Library is a collection of thousands of the most popular public domain books in an online readable format. The collection includes great classical literature and more recent works where the U.S. copyright has expired. These books are yours to read and use without restrictions.

Source Code - Want to change a program or know how it works? Open Source provides the source code for its programs so that anyone can use, modify or learn how to write those programs themselves. Visit the GNU source code repositories to download the source.


Study at Harvard, Stanford or MIT - Open edX provides free online courses from Harvard, MIT, Columbia, UC Berkeley and other top Universities. Hundreds of courses for almost all major subjects and course levels. Open edx also offers some paid courses and selected certifications.

Linux Manual Pages - A man or manual page is a form of software documentation found on Linux/Unix operating systems. Topics covered include computer programs (including library and system calls), formal standards and conventions, and even abstract concepts.