Fabian Franz 31ca3ac30f submodule: add --no-fetch parameter to update command
git submodule update --no-fetch makes it possible to use git submodule
update in complete offline mode by not fetching new revisions.

This does make sense in the following setup:

* There is an unstable and a stable branch in the super/master repository.
* The submodules might be at different revisions in the branches.
* You are at some place without internet connection ;)

With this patch it is now possible to change branches and update
the submodules to be at the recorded revision without online access.

Another advantage is that with -N the update operation is faster, because fetch is checking for new updates even if there was no fetch/pull on the super/master repository since the last update.

Signed-off-by: Fabian Franz <git@fabian-franz.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-02-07 00:44:49 -08:00
2009-01-21 22:46:52 -08:00
2008-12-17 21:56:48 -08:00
2009-02-05 19:40:39 -08:00
2008-10-26 16:21:08 -07:00
2008-10-21 17:58:11 -07:00
2009-01-28 11:33:03 -08:00
2008-12-07 15:13:02 -08:00
2008-10-08 08:05:43 -07:00
2009-01-28 11:33:51 -08:00
2009-02-05 19:40:39 -08:00
2009-01-25 17:13:29 -08:00
2009-01-25 17:13:29 -08:00
2009-02-05 19:40:39 -08:00
2009-01-28 11:33:03 -08:00
2008-12-21 02:47:21 -08:00
2009-01-05 13:01:01 -08:00
2008-10-10 08:39:20 -07:00
2008-10-10 08:39:20 -07:00
2009-01-17 18:30:41 -08:00
2008-11-02 16:36:40 -08:00
2009-01-25 17:13:11 -08:00
2009-01-25 17:13:34 -08:00
2008-12-21 02:47:21 -08:00
2008-11-11 14:49:50 -08:00
2009-02-04 13:07:02 -08:00
2009-01-17 18:30:41 -08:00
2009-02-05 19:40:35 -08:00
2008-12-03 14:27:17 -08:00
2009-01-29 00:12:52 -08:00
2009-01-17 18:30:41 -08:00
2009-02-05 19:40:36 -08:00
2008-12-07 15:13:02 -08:00
2008-11-23 19:23:34 -08:00
2009-02-05 19:40:39 -08:00
2008-10-25 12:09:31 -07:00
2008-12-21 02:47:21 -08:00
2009-02-05 19:40:39 -08:00
2009-01-19 22:18:29 -08:00
2009-01-19 22:18:29 -08:00
2009-01-29 00:12:52 -08:00
2009-01-11 13:21:57 -08:00
2009-01-28 15:00:27 -08:00
2009-01-17 18:30:41 -08:00
2008-10-09 11:26:17 -07:00
2009-01-31 17:42:26 -08:00
2009-01-21 23:52:16 -08:00
2009-02-04 16:30:43 -08:00
2009-02-04 16:30:43 -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 "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
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
No description provided
Readme 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%