Junio C Hamano 79a1e6b432 checkout: notice when the switched branch is behind or forked
When you are switching to a branch that is marked to merge from
somewhere else, e.g. when you have:

    [branch "next"]
            remote = upstream
            merge = refs/heads/next
    [remote "upstream"]
            url = ...
            fetch = refs/heads/*:refs/remotes/linus/*

and you say "git checkout next", the branch you checked out
may be behind, and you may want to update from the upstream
before continuing to work.

This patch makes the command to check the upstream (in this
example, "refs/remotes/linus/next") and our branch "next", and:

    (1) if they match, nothing happens;

    (2) if you are ahead (i.e. the upstream is a strict ancestor
        of you), one line message tells you so;

    (3) otherwise, you are either behind or you and the upstream
        have forked.  One line message will tell you which and
        then you will see a "log --pretty=oneline --left-right".

We could enhance this with an option that tells the command to
check if there is no local change, and automatically fast
forward when you are truly behind.  But I ripped out that change
because I was unsure what the right way should be to allow users
to control it (issues include that checkout should not become
automatically interactive).

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-02-16 17:17:09 -08:00
2007-06-07 00:04:01 -07:00
2007-11-11 12:10:35 -08:00
2008-02-16 15:05:02 -08:00
2008-01-20 17:05:11 -08:00
2008-01-20 16:58:38 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2008-02-16 15:05:02 -08:00
2007-11-15 21:23:47 -08:00
2007-12-19 17:24:04 -08:00
2007-10-19 01:18:55 -04:00
2007-05-30 15:03:50 -07:00
2008-01-16 15:35:35 -08:00
2007-06-07 00:04:01 -07:00
2008-01-16 15:35:35 -08:00
2008-01-07 14:02:25 -08:00
2007-12-19 14:59:11 -08:00
2007-11-09 00:21:44 -08:00
2008-01-16 15:35:35 -08:00
2007-12-04 17:07:10 -08:00
2008-01-16 15:35:35 -08:00
2008-01-16 15:35:35 -08:00
2008-02-16 15:05:02 -08:00
2008-01-16 15:35:35 -08:00
2007-09-26 02:27:06 -07:00
2007-12-05 17:57:11 -08:00
2008-01-16 15:35:35 -08:00
2008-01-16 09:10:34 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2008-01-04 16:05:23 -08:00
2007-06-07 00:04:01 -07:00
2008-01-03 01:23:12 -08:00
2007-11-17 21:39:37 -08:00
2007-11-28 17:06:57 -08:00
2007-10-26 23:17:23 -07:00
2008-01-11 21:40:55 -08:00
2008-02-16 15:05:02 -08:00
2007-11-14 14:04:19 -08:00
2007-10-02 17:35:29 -07:00
2007-10-03 04:28:24 -07:00
2007-10-26 23:27:23 -07:00
2008-02-16 15:05:02 -08:00
2007-12-13 23:04:26 -08:00
2008-02-09 23:16:51 -08:00
2007-12-13 23:04:26 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-11-02 16:27:37 -07:00
2007-11-02 16:27:37 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-12-26 17:13:36 -08:00
2007-12-26 17:13:36 -08:00
2008-01-07 22:41:43 -08:00
2007-12-03 23:43:07 -08:00
2007-12-26 11:57:36 -08:00
2007-11-09 21:14:10 -08:00
2007-06-07 00:04:01 -07:00
2008-01-03 01:23:12 -08:00
2007-05-01 02:59:08 -07:00
2007-12-09 00:55:55 -08:00
2007-09-19 03:22:30 -07: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/tutorial.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 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%