Christian Couder 6aa1fb2271 parse-options: add parse_options_takes_argument()
Whether an option takes a value, and therefore consumes the next
argument when that value is not stuck to it with an '=', is decided by
its type and its flags. That rule is currently open-coded in
show_gitcomp(), which needs it to decide if it should append an '=' to
the option it completes.

A following commit will need the same rule to find out which options an
early scan of the command line has to skip along with their value.

So let's factor that rule out into a new parse_options_takes_argument()
function, and let's use it in show_gitcomp().

Note that an option with PARSE_OPT_LASTARG_DEFAULT only consumes the
next argument when it isn't the last one. It is considered as taking a
value by parse_options_takes_argument(), as an early scan can easily
check whether there is a next argument, and would otherwise wrongly
take that argument for an option. show_gitcomp() keeps not appending
an '=' to such an option though, as it already did, since its value is
optional.

Signed-off-by: Christian Couder <christian.couder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2026-11-02 11:02:27 -08:00
2026-07-19 10:42:15 -07:00
2026-08-31 08:25:00 -07:00
2026-02-03 09:41:52 -08:00
…
2026-05-21 12:06:48 +09:00
…
…
…
…
…
…
…
2025-12-07 07:28:13 +09:00
…
…
…
…
…
…
…
2026-02-07 17:41:03 -08:00
2026-05-21 12:06:48 +09:00
2026-02-23 13:23:41 -08:00
2026-02-23 13:23:41 -08:00
…
…
2026-06-08 00:21:35 +09:00
…
2026-07-16 14:10:08 -07:00
2026-07-16 14:10:08 -07:00
…
…
2026-06-05 22:27:24 +09:00
…
2026-05-30 07:07:27 +09:00
2026-08-24 13:17:51 -07:00
2026-05-30 07:07:27 +09:00
2026-07-30 10:32:03 -07:00
…
…
2026-03-23 08:33:10 -07:00
…
…
…
2026-07-06 15:50:25 -07:00
…
…
…
…
…
…
2026-05-14 15:59:25 +09:00
2026-05-14 15:59:25 +09:00
2026-06-15 07:42:00 -07:00
2026-07-16 23:05:47 -07:00
…
…
…
…
…
…
…
2026-07-15 13:24:19 -07:00
…
…
2026-08-18 09:31:36 -07:00
2026-07-31 08:52:16 -07:00
2026-07-31 08:52:16 -07:00
…
2026-08-18 09:31:36 -07:00
…
2025-11-25 12:15:59 -08:00
2025-11-25 12:15:59 -08:00
2026-05-15 04:50:45 +09:00
2026-05-15 04:50:45 +09:00
…
2026-07-06 15:50:23 -07:00
2026-06-09 10:04:50 +09:00
…
…
2026-05-19 12:14:03 +09:00
2026-05-19 12:14:03 +09:00
…
…
…
2026-07-06 15:50:25 -07:00
2026-07-15 13:24:19 -07:00
2026-08-15 09:20:27 -07:00
…
…
2026-08-06 21:24:25 -07:00
2026-07-07 10:49:40 -07:00
…
2026-08-18 09:31:36 -07:00
2026-05-13 00:48:42 +09:00
…
…
…
…
…
2026-07-14 12:54:25 -07:00
2026-07-14 12:54:25 -07:00
…
…
2026-07-07 10:49:40 -07:00
…
2026-05-30 07:07:27 +09:00
2026-01-09 18:36:17 -08:00
2026-07-07 17:48:57 -07:00
2026-07-23 07:14:34 -07:00
…
…
…
2026-02-08 15:16:49 -08:00
2026-02-08 15:16:49 -08:00
…
…
…

GitHub build status GitLab build status

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 https://git-scm.com/ including full documentation and Git related tools.

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

Those wishing to help with error message, usage and informational message string translations (localization l10) should see po/README.md (a po file is a Portable Object file that holds the translations).

To subscribe to the list, send an email to git+subscribe@vger.kernel.org (see https://subspace.kernel.org/subscribing.html for details). The mailing list archives are available at https://lore.kernel.org/git/, https://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

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
Languages
C 49.8%
Shell 39.8%
Perl 4.3%
Tcl 3%
Python 0.8%
Other 2.1%