1
0
mirror of https://github.com/git/git.git synced 2025-03-23 15:36:47 +00:00
Jens Lehmann 46a958b3da Add the option "--ignore-submodules" to "git status"
In some use cases it is not desirable that "git status" considers
submodules that only contain untracked content as dirty. This may happen
e.g. when the submodule is not under the developers control and not all
build generated files have been added to .gitignore by the upstream
developers. Using the "untracked" parameter for the "--ignore-submodules"
option disables checking for untracked content and lets git diff report
them as changed only when they have new commits or modified content.

Sometimes it is not wanted to have submodules show up as changed when they
just contain changes to their work tree (this was the behavior before
1.7.0). An example for that are scripts which just want to check for
submodule commits while ignoring any changes to the work tree. Also users
having large submodules known not to change might want to use this option,
as the - sometimes substantial - time it takes to scan the submodule work
tree(s) is saved when using the "dirty" parameter.

And if you want to ignore any changes to submodules, you can now do that
by using this option without parameters or with "all" (when the config
option status.submodulesummary is set, using "all" will also suppress the
output of the submodule summary).

A new function handle_ignore_submodules_arg() is introduced to parse this
option new to "git status" in a single location, as "git diff" already
knew it.

Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-06-25 11:30:25 -07:00
2010-02-07 15:52:28 -08:00
2010-05-02 08:27:58 -07:00
2010-01-29 22:11:00 -08:00
2010-01-29 22:11:00 -08:00
2010-01-16 20:39:59 -08:00
2010-01-16 20:39:59 -08:00
2009-11-23 22:30:08 -08:00
2010-01-29 23:36:13 -08:00
2010-01-20 14:39:52 -08:00
2010-03-20 11:29:35 -07:00
2010-01-13 11:58:34 -08:00
2010-01-20 14:37:25 -08:00
2010-03-24 16:26:43 -07:00
2010-02-11 23:06:32 -08:00
2009-12-13 23:40:24 -08:00
2010-03-20 11:29:19 -07:00
2010-04-03 12:28:44 -07:00
2010-03-20 11:29:35 -07:00
2010-03-15 00:52:06 -07:00
2010-04-03 12:28:39 -07:00
2010-03-20 11:29:36 -07:00
2010-01-21 20:03:45 -08:00
2010-01-12 01:06:09 -08:00
2010-01-12 01:06:09 -08:00
2010-05-28 16:59:36 -07:00
2010-03-24 16:26:43 -07:00
2010-01-17 22:49:36 -08:00
2010-01-17 22:49:36 -08:00
2010-04-22 23:04:21 -07:00
2010-03-15 00:58:50 -07:00
2010-01-09 23:34:10 -08:00
2010-01-20 14:46:35 -08:00
2010-03-24 16:26:43 -07:00
2010-03-24 16:26:43 -07:00
2010-06-05 08:41:39 -07:00
2010-01-21 20:03:45 -08:00
2009-11-04 17:58:15 -08:00
2010-01-20 20:28:50 -08:00
2010-01-17 22:49:36 -08:00
2010-01-24 17:35:58 -08:00
2010-01-24 17:35:58 -08:00
2009-11-22 16:14:48 -08:00
2010-01-16 20:39:59 -08:00
2010-01-16 20:39:59 -08:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

Git is a fast, scalable, distributed revision control system with an
unusually rich command set that provides both high-level operations
and full access to internals.

Git is an Open Source project covered by the GNU General Public License.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.

See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.txt for documentation of each command.
If git has been correctly installed, then the tutorial can also be
read with "man gittutorial" or "git help tutorial", and the
documentation of each command with "man git-commandname" or "git help
commandname".

CVS users may also want to read Documentation/gitcvs-migration.txt
("man gitcvs-migration" or "git help cvs-migration" if git is
installed).

Many Git online resources are accessible from http://git-scm.com/
including full documentation and Git related tools.

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to git@vger.kernel.org. To subscribe
to the list, send an email with just "subscribe git" in the body to
majordomo@vger.kernel.org. The mailing list archives are available at
http://marc.theaimsgroup.com/?l=git and other archival sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 797 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%