Brandon Casey 9d58c4a3e3 t/t9802: explicitly name the upstream branch to use as a base
Prior to commit fa83a33b, the 'git checkout' DWIMery would create a
new local branch if the specified branch name did not exist and it
matched exactly one ref in the "remotes" namespace.  It searched
the "remotes" namespace for matching refs using a simple comparison
of the trailing portion of the remote ref names.  This approach
could sometimes produce false positives or negatives.

Since fa83a33b, the DWIMery more strictly excludes the remote name
from the ref comparison by iterating through the remotes that are
configured in the .gitconfig file.  This has the side-effect that
any refs that exist in the "remotes" namespace, but do not match
the destination side of any remote refspec, will not be used by
the DWIMery.

This change in behavior breaks the tests in t9802 which relied on
the old behavior of searching all refs in the remotes namespace,
since the git-p4 script does not configure any remotes in the
.gitconfig.  Let's work around this in these tests by explicitly
naming the upstream branch to base the new local branch on when
calling 'git checkout'.

Signed-off-by: Brandon Casey <drafnel@gmail.com>
Acked-by: Pete Wyckoff <pw@padd.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2013-06-18 09:16:58 -07:00
2013-05-09 13:32:54 -07:00
2013-04-04 13:03:34 -07:00
2012-10-25 06:42:02 -04:00
2012-10-25 06:42:02 -04:00
2012-10-29 03:08:30 -04:00
2013-01-23 21:19:10 -08:00
2013-05-29 14:23:04 -07:00
2013-04-12 13:54:01 -07:00
2013-02-26 09:16:58 -08:00
2013-04-01 08:59:37 -07:00
2013-05-29 14:23:04 -07:00
2013-02-17 15:25:52 -08:00
2012-11-28 13:52:54 -08:00
2013-03-26 13:15:24 -07:00
2013-05-17 12:19:20 -07:00
2012-04-06 10:15:11 -07:00
2012-05-03 15:13:31 -07:00
2013-04-06 18:56:46 -07:00
2013-04-19 13:31:08 -07:00
2013-04-19 13:31:08 -07:00
2013-04-11 17:39:05 -07:00
2013-04-12 12:25:08 -07:00
2013-01-20 17:06:53 -08:00
2013-04-03 09:18:01 -07:00
2012-09-11 11:23:54 -07:00
2012-10-17 22:42:40 -07:00
2013-03-18 08:06:28 -07:00
2012-10-29 03:08:30 -04:00
2013-05-29 14:23:04 -07:00
2012-08-03 12:11:07 -07:00
2013-04-05 12:39:38 -07:00
2013-02-05 16:13:32 -08:00
2013-04-03 09:18:01 -07:00
2013-03-26 13:15:56 -07:00
2013-05-09 13:31:17 -07:00
2013-04-01 08:59:37 -07:00
2013-04-12 13:54:01 -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 version 2 (some parts of it are under different licenses,
compatible with the GPLv2). It was originally written by Linus
Torvalds with help of a group of hackers around the net.

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://news.gmane.org/gmane.comp.version-control.git/,
http://marc.info/?l=git and other archival sites.

The maintainer frequently sends the "What's cooking" reports that
list the current status of various development topics to the mailing
list.  The discussion following them give a good reference for
project status, development direction and remaining tasks.
Description
No description provided
Readme 774 MiB
Languages
C 50.4%
Shell 38.7%
Perl 4.4%
Tcl 3.1%
Python 0.8%
Other 2.4%