Derrick Stolee d585f0e799 sparse-checkout: write escaped patterns in cone mode
If a user somehow creates a directory with an asterisk (*) or backslash
(\), then the "git sparse-checkout set" command will struggle to provide
the correct pattern in the sparse-checkout file. When not in cone mode,
the provided pattern is written directly into the sparse-checkout file.
However, in cone mode we expect a list of paths to directories and then
we convert those into patterns.

However, there is some care needed for the timing of these escapes. The
in-memory pattern list is used to update the working directory before
writing the patterns to disk. Thus, we need the command to have the
unescaped names in the hashsets for the cone comparisons, then escape
the patterns later.

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-01-31 13:05:29 -08:00
2019-10-24 13:34:03 +09:00
2019-05-14 16:45:01 +09:00
2019-11-10 18:02:15 +09:00
2019-09-28 14:04:16 +09:00
2019-10-15 13:48:02 +09:00
2018-09-12 15:15:34 -07:00
2019-08-19 15:04:58 -07:00
2019-10-15 13:48:02 +09:00
2019-07-19 11:30:20 -07:00
2019-07-09 15:25:44 -07:00
2019-07-09 15:25:44 -07:00
2019-08-19 15:04:58 -07:00
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2019-11-22 16:11:44 +09:00
2019-10-11 14:24:46 +09:00
2019-09-12 11:03:51 -07:00
2019-07-09 15:25:43 -07:00
2019-05-05 15:20:10 +09:00
2019-10-15 13:48:02 +09:00
2019-08-19 15:04:57 -07:00
2019-10-15 13:48:02 +09:00
2019-11-22 16:11:44 +09:00
2019-11-22 16:11:44 +09:00
2019-07-19 11:30:20 -07:00
2019-07-25 13:59:20 -07:00
2019-08-30 10:22:42 -07:00
2019-09-30 13:19:24 +09:00
2019-08-15 12:37:10 -07:00
2019-04-22 11:14:43 +09:00
2017-09-06 17:19:54 +09:00
2018-08-29 13:05:35 -07:00
2019-01-14 12:13:04 -08:00
2019-10-23 12:05:05 +09:00
2019-07-19 11:30:20 -07:00
2019-07-19 11:30:20 -07:00
2019-05-05 15:20:10 +09:00
2019-10-15 13:48:02 +09:00
2019-11-10 18:02:14 +09:00
2019-02-06 22:05:23 -08:00
2019-02-05 14:26:09 -08:00
2018-11-02 12:14:21 +09:00
2019-09-17 09:39:16 -07:00
2019-10-15 13:48:02 +09:00
2019-10-15 13:48:02 +09:00
2019-10-12 21:29:30 +05:30
2019-10-15 13:48:02 +09:00
2018-08-15 15:08:23 -07:00
2019-04-01 11:57:39 +09:00
2019-11-10 18:02:17 +09:00
2019-08-19 15:04:59 -07:00
2019-10-15 13:48:02 +09:00
2019-05-05 15:20:10 +09:00
2019-09-30 13:19:26 +09:00
2019-10-11 14:24:46 +09:00
2019-10-11 14:24:48 +09:00
2018-06-01 15:06:37 +09:00
2019-02-05 14:26:11 -08:00
2018-12-09 12:37:32 +09:00
2019-09-05 14:10:18 -07:00
2019-09-05 14:10:18 -07:00
2019-05-13 23:50:35 +09:00
2019-08-13 12:21:33 -07:00
2019-05-05 15:20:10 +09:00
2019-09-03 15:10:53 -07:00
2019-10-12 10:57:39 +09:00
2019-10-09 14:01:00 +09:00
2018-10-19 13:34:02 +09:00
2019-10-11 14:24:46 +09: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). 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.

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 587 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%