1
0
mirror of https://github.com/git/git.git synced 2025-04-23 01:37:47 +00:00
Brandon Williams be80a2392f grep: fix bug when recursing with relative pathspec
When using the --recurse-submodules flag with a relative pathspec which
includes "..", an error is produced inside the child process spawned for
a submodule.  When creating the pathspec struct in the child, the ".."
is interpreted to mean "go up a directory" which causes an error stating
that the path ".." is outside of the repository.

While it is true that ".." is outside the scope of the submodule, it is
confusing to a user who originally invoked the command where ".." was
indeed still inside the scope of the superproject.  Since the child
process launched for the submodule has some context that it is operating
underneath a superproject, this error could be avoided.

This patch fixes the bug by passing the 'prefix' to the child process.
Now each child process that works on a submodule has two points of
reference to the superproject: (1) the 'super_prefix' which is the path
from the root of the superproject down to root of the submodule and (2)
the 'prefix' which is the path from the root of the superproject down to
the directory where the user invoked the git command.

With these two pieces of information a child process can correctly
interpret the pathspecs provided by the user as well as being able to
properly format its output relative to the directory the user invoked
the original command from.

Signed-off-by: Brandon Williams <bmwill@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-03-17 11:54:50 -07:00
2017-02-16 14:45:13 -08:00
2017-02-24 10:49:58 -08:00
2016-10-20 09:33:17 -07:00
2017-01-25 14:42:37 -08:00
2017-02-02 13:36:57 -08:00
2017-02-02 13:36:55 -08:00
2017-01-30 14:07:52 -08:00
2016-11-22 13:55:20 -08:00
2016-11-22 13:55:20 -08:00
2017-01-25 14:42:37 -08:00
2016-08-12 09:47:37 -07:00
2016-12-06 13:27:11 -08:00
2016-10-31 13:15:21 -07:00
2016-07-27 14:15:51 -07:00
2017-01-30 14:23:00 -08:00
2017-02-15 12:54:19 -08:00
2016-10-27 14:58:50 -07:00
2016-09-29 15:42:18 -07:00
2016-12-12 15:15:07 -08:00
2017-02-15 12:54:19 -08:00
2017-02-16 14:45:12 -08:00
2016-12-19 14:45:35 -08:00
2016-10-14 01:36:12 +00:00
2017-02-24 10:49:58 -08:00
2017-02-15 12:54:19 -08:00
2016-09-29 15:42:18 -07:00
2017-01-30 14:17:00 -08:00
2016-12-07 11:31:59 -08:00
2017-02-02 13:36:57 -08:00
2017-01-30 14:17:00 -08:00
2016-12-07 11:31:59 -08:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2016-09-26 16:09:18 -07:00
2017-01-30 14:17:00 -08:00
2016-09-29 15:42:18 -07:00
2017-01-30 14:17:00 -08:00
2016-09-29 15:42:18 -07:00
2016-10-17 13:25:21 -07:00
2017-01-30 14:17:00 -08:00
2016-07-28 11:26:03 -07:00
2016-07-28 11:26:03 -07:00
2017-01-31 13:15:00 -08:00
2017-01-31 13:14:58 -08:00
2017-01-17 15:19:11 -08:00
2016-09-29 15:42:18 -07:00
2016-10-10 14:03:46 -07:00
2017-01-30 14:17:00 -08:00
2016-08-05 09:28:17 -07:00
2016-09-29 15:42:18 -07:00
2017-01-31 13:14:56 -08:00
2016-09-26 18:16:23 -07:00
2017-02-02 13:36:55 -08:00
2017-02-03 11:25:19 -08: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 https://public-inbox.org/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
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 869 MiB
Languages
C 49.9%
Shell 38.6%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%