1
0
mirror of https://github.com/git/git.git synced 2025-04-21 03:17:41 +00:00
Paul Tan eb2a8d9ed3 pull: handle git-fetch's options as well
While parsing the command-line arguments, git-pull stops parsing at the
first unrecognized option, assuming that any subsequent options are for
git-fetch, and can thus be kept in the shell's positional parameters
list, so that it can be passed to git-fetch via the expansion of "$@".

However, certain functions in git-pull assume that the positional
parameters do not contain any options:

* error_on_no_merge_candidates() uses the number of positional
  parameters to determine which error message to print out, and will
  thus print the wrong message if git-fetch's options are passed in as
  well.

* the call to get_remote_merge_branch() assumes that the positional
  parameters only contains the optional repo and refspecs, and will
  thus silently fail if git-fetch's options are passed in as well.

* --dry-run is a valid git-fetch option, but if provided after any
  git-fetch options, it is not recognized by git-pull and thus git-pull
  will continue to run the merge or rebase.

Fix these bugs by teaching git-pull to parse git-fetch's options as
well. Add tests to prevent regressions.

This removes the limitation where git-fetch's options have to come after
git-merge's and git-rebase's options on the command line. Update the
documentation to reflect this.

Signed-off-by: Paul Tan <pyokagan@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-06-02 13:36:22 -07:00
2015-05-26 13:24:46 -07:00
2015-04-18 18:35:48 -07:00
2015-03-12 13:45:18 -07:00
2015-05-05 21:00:23 -07:00
2015-05-05 21:00:23 -07:00
2015-05-05 21:00:23 -07:00
2015-03-10 20:53:52 -07:00
2015-05-05 21:00:23 -07:00
2015-05-19 13:17:55 -07:00
2015-05-20 10:19:12 -07:00
2015-05-19 13:17:49 -07:00
2015-06-01 12:45:15 -07:00
2015-05-26 13:24:46 -07:00
2015-05-11 14:23:48 -07:00
2015-06-01 12:45:14 -07:00
2015-05-26 13:49:59 -07:00
2015-05-11 14:23:39 -07:00
2015-03-13 22:43:11 -07:00
2015-03-27 13:02:32 -07:00
2015-05-22 12:41:45 -07:00
2015-05-22 12:41:51 -07:00
2015-06-01 12:45:19 -07:00
2015-03-23 11:12:58 -07:00
2015-05-11 14:24:01 -07:00
2015-05-26 13:24:46 -07:00
2015-05-22 12:41:55 -07:00
2015-05-11 14:23:39 -07:00
2015-05-26 13:49:59 -07:00
2015-05-05 21:00:23 -07:00
2015-05-05 21:00:23 -07:00
2015-06-01 12:45:15 -07:00
2015-05-11 14:23:39 -07:00
2015-03-22 21:39:18 -07:00
2015-06-01 12:45:19 -07:00
2015-05-26 13:24:46 -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/giteveryday.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
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 866 MiB
Languages
C 49.9%
Shell 38.6%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%