Carlos Martín Nieto b347d06bf0 branch: deprecate --set-upstream and show help if we detect possible mistaken use
This interface is error prone, and a better one (--set-upstream-to)
exists. Add a message listing the alternatives and suggest how to fix
a --set-upstream invocation in case the user only gives one argument
which causes a local branch with the same name as a remote-tracking
one to be created. The typical case is

    git branch --set-upstream origin/master

when the user meant

    git branch --set-upstream master origin/master

assuming that the current branch is master. Show a message telling the
user how to undo their action and get what they wanted. For the
command above, the message would be

The --set-upstream flag is deprecated and will be removed. Consider using --track or --set-upstream-to
Branch origin/master set up to track local branch master.

If you wanted to make 'master' track 'origin/master', do this:

    git branch -d origin/master
    git branch --set-upstream-to origin/master

Signed-off-by: Carlos Martín Nieto <cmn@elego.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-08-30 12:07:39 -07:00
2012-04-02 15:06:25 -07:00
2012-08-16 13:57:51 +01:00
2012-07-13 15:37:04 -07:00
2012-07-15 21:39:17 -07:00
2012-07-23 20:55:21 -07:00
2012-07-22 12:55:07 -07:00
2012-07-22 12:56:27 -07:00
2012-07-04 23:40:12 -07:00
2012-03-07 12:12:59 -08:00
2012-01-08 15:08:03 -08:00
2012-07-31 09:43:07 -07:00
2012-07-25 15:47:05 -07:00
2012-07-31 09:41:52 -07:00
2012-07-15 21:38:32 -07:00
2012-07-31 09:41:52 -07:00
2012-08-19 17:02:11 -07:00
2012-06-25 11:55:51 -07:00
2012-04-06 10:15:11 -07:00
2012-07-25 11:08:59 -07:00
2012-05-03 15:13:31 -07:00
2011-12-19 16:06:41 -08:00
2012-03-28 08:47:23 -07:00
2012-05-29 13:09:13 -07:00
2012-01-06 12:44:07 -08:00
2011-12-16 22:33:40 -08:00
2012-04-27 09:26:38 -07:00
2011-12-12 16:09:38 -08:00
2012-05-29 13:09:02 -07:00
2012-04-10 15:55:55 -07:00
2012-08-06 15:51:58 -07:00
2012-07-22 12:55:07 -07:00
2012-06-01 13:28:19 -07:00
2012-07-22 12:55:07 -07:00
2012-07-22 12:55:07 -07:00
2011-12-11 23:16:25 -08:00
2012-07-08 22:03:46 -07:00
2012-07-08 22:03:46 -07:00
2012-06-03 13:11:52 -07:00
2012-06-03 13:11:52 -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/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 (read
Documentation/SubmittingPatches for instructions on patch submission).
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 647 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%