Dragan Simic 6e9ef296e2 grep docs: describe --no-index further and improve formatting a bit
Improve the description of --no-index, to make it more clear to the users
what this option actually does under the hood, and what's its purpose.
Describe the dependency between --no-index and either of the --cached and
--untracked options, which cannot be used together.

As part of that, shuffle a couple of the options, to make the documentation
flow a bit better, because it makes more sense to describe first the options
that have something in common, and to after that describe an option that does
something differently.  In more detail, --cached and --untracked both leave
git-grep(1) in the usual state, in which it treats the directory as a local
git repository, unlike --no-index that makes git-grep(1) treat the directory
not as a git repository.

While there, improve the descriptions of grep worker threads a bit, to give
them better context.  Adjust the language a bit, to avoid addressing the
reader directly, which is in general preferred in technical documentation,
because it eliminates the possible element of persuading the user to do
something.  In other words, we should be telling the user what our software
can do, instead of telling the user what to do.

Also perform some minor formatting improvements, to make it clear it's the
git commands, command parameters, and configuration option names.

Signed-off-by: Dragan Simic <dsimic@manjaro.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2024-03-25 14:00:03 -07:00
2023-12-14 14:38:07 -08:00
2023-11-26 10:07:05 +09:00
2024-02-18 21:03:43 +08:00
2023-11-26 10:07:06 +09:00
2023-11-26 10:10:48 +09:00
2024-02-27 16:04:31 -08:00
2024-02-12 09:32:41 -08:00
2023-12-26 12:04:32 -08:00
2023-12-26 12:04:32 -08:00
2024-03-05 13:04:26 -08:00
2023-11-26 10:10:48 +09:00
2023-07-25 12:05:24 -07:00
2024-01-23 10:40:10 -08:00
2023-11-26 10:10:48 +09:00
2024-03-06 08:10:58 -08:00
2023-07-06 11:54:48 -07:00
2024-02-12 09:32:41 -08:00
2023-04-10 08:46:40 -07:00
2024-02-15 15:14:48 -08:00
2024-03-07 15:59:40 -08:00
2023-08-31 15:51:07 -07:00
2023-04-17 21:15:56 +02:00
2023-11-26 10:07:05 +09:00
2024-03-05 09:44:44 -08:00
2023-11-26 10:07:05 +09:00
2023-06-28 14:06:39 -07:00
2023-12-26 12:04:32 -08:00
2023-06-28 14:06:39 -07:00
2023-11-26 10:07:05 +09:00
2023-11-26 10:07:05 +09:00
2023-11-26 10:07:05 +09:00
2023-11-26 10:07:05 +09:00
2024-02-26 18:10:23 -08:00
2024-02-26 09:35:40 -08:00
2024-02-26 09:35:40 -08:00
2024-02-26 18:10:24 -08:00
2023-06-21 13:39:54 -07:00
2024-03-07 15:59:41 -08:00
2023-12-14 14:38:08 -08:00
2024-02-26 15:34:01 -08:00
2024-02-26 15:34:01 -08:00
2023-06-28 14:06:39 -07:00
2024-02-07 08:28:37 -08:00
2024-02-07 08:28:37 -08:00
2023-11-26 10:07:05 +09:00
2023-09-15 17:08:46 -07:00
2024-01-08 14:05:15 -08:00
2024-03-14 14:05:24 -07:00
2024-03-05 09:44:44 -08:00
2024-03-05 09:44:44 -08:00
2024-02-26 18:10:25 -08:00
2024-03-07 15:59:41 -08:00
2024-03-21 14:55:13 -07:00
2023-11-26 10:07:05 +09:00
2024-03-02 11:12:16 -08:00
2023-12-27 14:52:24 -08:00
2023-09-15 17:08:46 -07:00
2023-11-26 10:07:05 +09:00
2023-03-17 14:03:09 -07:00
2024-03-14 14:05:24 -07:00
2023-06-28 14:06:39 -07:00
2023-11-26 10:07:05 +09:00
2023-11-26 10:07:05 +09:00
2023-04-04 14:28:27 -07:00
2023-05-17 10:11:41 -07:00

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.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).

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
Description
No description provided
Readme 582 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%