Johannes Schindelin e459b073fb remote rename: more carefully determine whether a remote is configured
One of the really nice features of the ~/.gitconfig file is that users
can override defaults by their own preferred settings for all of their
repositories.

One such default that some users like to override is whether the
"origin" remote gets auto-pruned or not. The user would simply call

	git config --global remote.origin.prune true

and from now on all "origin" remotes would be pruned automatically when
fetching into the local repository.

There is just one catch: now Git thinks that the "origin" remote is
configured, even if the repository config has no [remote "origin"]
section at all, as it does not realize that the "prune" setting was
configured globally and that there really is no "origin" remote
configured in this repository.

That is a problem e.g. when renaming a remote to a new name, when Git
may be fooled into thinking that there is already a remote of that new
name.

Let's fix this by paying more attention to *where* the remote settings
came from: if they are configured in the local repository config, we
must not overwrite them. If they were configured elsewhere, we cannot
overwrite them to begin with, as we only write the repository config.

There is only one caller of remote_is_configured() (in `git fetch`) that
may want to take remotes into account even if they were configured
outside the repository config; all other callers essentially try to
prevent the Git command from overwriting settings in the repository
config.

To accommodate that fact, the remote_is_configured() function now
requires a parameter that states whether the caller is interested in all
remotes, or only in those that were configured in the repository config.

Many thanks to Jeff King whose tireless review helped with settling for
nothing less than the current strategy.

This fixes https://github.com/git-for-windows/git/issues/888

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-01-19 14:04:23 -08:00
2016-12-05 11:25:02 -08:00
2016-09-26 17:46:44 -07:00
2016-07-19 13:22:22 -07:00
2016-07-19 13:22:16 -07:00
2016-08-12 09:47:37 -07:00
2016-08-19 15:34:14 -07:00
2016-07-20 12:11:09 -07:00
2016-07-20 12:11:09 -07:00
2016-07-27 14:15:51 -07:00
2016-07-25 14:13:32 -07:00
2016-07-19 13:22:19 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2016-08-11 14:35:42 -07:00
2016-10-28 09:02:44 -07:00
2016-07-06 13:38:06 -07:00
2016-07-19 13:22:16 -07:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2016-09-25 16:44:13 -07:00
2016-07-29 11:05:06 -07:00
2016-09-25 16:44:13 -07:00
2016-10-28 09:01:23 -07:00
2016-07-28 11:26:03 -07:00
2016-07-28 11:26:03 -07:00
2016-07-25 14:13:33 -07:00
2016-12-05 11:25:02 -08:00
2016-08-12 09:47:39 -07:00
2016-08-19 15:34:16 -07:00
2016-07-14 15:50:41 -07:00
2016-08-24 08:41:22 -07:00
2016-07-01 15:09:10 -07:00
2016-09-25 16:44:13 -07:00
2016-10-28 09:01:23 -07:00
2016-08-05 09:28:17 -07:00
2016-08-11 14:35:42 -07:00
2016-07-14 15:50:41 -07:00

Git - fast, scalable, distributed revision control system

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.

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

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-.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).

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.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (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
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%