Elijah Newren bb8b5e9a90 sparse-checkout: pay attention to prefix for {set, add}
In cone mode, non-option arguments to set & add are clearly paths, and
as such, we should pay attention to prefix.

In non-cone mode, it is not clear that folks intend to provide paths
since the inputs are gitignore-style patterns.  Paying attention to
prefix would prevent folks from doing things like
   git sparse-checkout add /.gitattributes
   git sparse-checkout add '/toplevel-dir/*'
In fact, the former will result in
   fatal: '/.gitattributes' is outside repository...
while the later will result in
   fatal: Invalid path '/toplevel-dir': No such file or directory
despite the fact that both are valid gitignore-style patterns that would
select real files if added to the sparse-checkout file.  This might lead
people to just use the path without the leading slash, potentially
resulting in them grabbing files with the same name throughout the
directory hierarchy contrary to their expectations.  See also [1] and
[2].  Adding prefix seems to just be fraught with error; so for now
simply throw an error in non-cone mode when sparse-checkout set/add are
run from a subdirectory.

[1] https://lore.kernel.org/git/e1934710-e228-adc4-d37c-f706883bd27c@gmail.com/
[2] https://lore.kernel.org/git/CABPp-BHXZ-XLxY0a3wCATfdq=6-EjW62RzbxKAoFPeXfJswD2w@mail.gmail.com/

Helped-by: Junio Hamano <gitster@pobox.com>
Reviewed-by: Derrick Stolee <derrickstolee@github.com>
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-02-20 00:01:15 -08:00
2021-12-15 09:39:49 -08:00
2021-12-15 09:39:49 -08:00
2022-02-11 16:55:57 -08:00
2022-02-11 16:55:57 -08:00
2022-02-11 16:56:01 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-10-29 10:22:40 -07:00
2022-01-23 09:40:52 +01:00
2021-12-15 09:39:47 -08:00
2021-08-12 14:00:52 -07:00
2022-01-07 15:19:34 -08:00
2021-03-08 09:56:34 -08:00
2021-04-27 16:31:39 +09:00
2021-05-07 12:47:41 +09:00
2022-01-07 15:19:34 -08:00
2021-12-10 14:35:12 -08:00
2022-02-05 09:42:32 -08:00
2021-07-13 16:52:50 -07:00
2022-01-07 15:19:34 -08:00
2021-03-13 16:00:09 -08:00
2022-01-05 14:01:28 -08:00
2021-12-15 09:39:45 -08:00
2022-01-05 14:01:31 -08:00
2021-11-04 12:38:09 -07:00
2021-03-13 16:00:09 -08:00
2022-01-10 11:52:56 -08:00
2022-01-03 16:24:15 -08:00
2021-09-23 13:44:48 -07:00
2022-01-28 16:48:42 -08:00
2022-02-09 14:21:00 -08:00
2022-02-05 09:42:30 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-10-11 10:21:47 -07:00
2022-02-11 16:55:57 -08:00
2021-10-28 15:32:14 -07:00
2021-03-13 16:00:09 -08:00
2021-04-27 16:31:39 +09:00
2022-01-03 16:24:15 -08:00
2022-01-03 16:24:15 -08:00
2022-01-03 16:24:15 -08:00
2021-03-13 16:00:09 -08:00
2022-02-05 09:42:31 -08:00
2021-03-13 16:00:09 -08:00
2021-09-20 15:20:40 -07:00
2021-03-13 16:00:09 -08:00
2021-08-24 15:32:37 -07:00
2022-01-03 16:24:15 -08:00
2022-01-03 16:24:15 -08:00
2021-10-25 16:06:58 -07:00
2022-01-05 14:01:28 -08:00
2021-05-04 11:52:02 +09:00
2021-05-04 11:52:02 +09:00
2021-12-15 09:39:52 -08:00
2022-01-05 14:01:28 -08: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 with just "subscribe git" in the body to majordomo@vger.kernel.org (not the Git list). The mailing list archives are available at https://lore.kernel.org/git/, http://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 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%