Victoria Dye 71471b2a7c reset: preserve skip-worktree bit in mixed reset
Change `update_index_from_diff` to set `skip-worktree` when applicable for
new index entries. When `git reset --mixed <tree-ish>` is run, entries in
the index with differences between the pre-reset HEAD and reset <tree-ish>
are identified and handled with `update_index_from_diff`. For each file, a
new cache entry in inserted into the index, created from the <tree-ish> side
of the reset (without changing the working tree). However, the newly-created
entry must have `skip-worktree` explicitly set in either of the following
scenarios:

1. the file is in the current index and has `skip-worktree` set
2. the file is not in the current index but is outside of a defined sparse
   checkout definition

Not setting the `skip-worktree` bit leads to likely-undesirable results for
a user. It causes `skip-worktree` settings to disappear on the
"diff"-containing files (but *only* the diff-containing files), leading to
those files now showing modifications in `git status`. For example, when
running `git reset --mixed` in a sparse checkout, some file entries outside
of sparse checkout could show up as deleted, despite the user never deleting
anything (and not wanting them on-disk anyway).

Additionally, add a test to `t7102` to ensure `skip-worktree` is preserved
in a basic `git reset --mixed` scenario and update a failure-documenting
test from 19a0acc (t1092: test interesting sparse-checkout scenarios,
2021-01-23) with new expected behavior.

Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Victoria Dye <vdye@github.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-10-27 15:05:11 -07:00
2021-10-03 21:49:17 -07:00
2021-09-20 15:20:39 -07:00
2021-10-06 13:40:32 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-07-22 13:05:54 -07:00
2021-07-13 16:52:50 -07:00
2021-08-12 14:00:52 -07:00
2021-05-10 16:59:47 +09:00
2021-03-08 09:56:34 -08:00
2021-03-13 16:00:09 -08:00
2021-04-27 16:31:39 +09:00
2021-05-07 12:47:41 +09:00
2021-07-13 16:52:50 -07:00
2021-03-13 16:00:09 -08:00
2021-09-20 15:20:39 -07:00
2021-03-13 16:00:09 -08:00
2021-09-09 15:49:04 -07:00
2021-09-23 13:44:48 -07:00
2021-08-24 15:33:23 -07:00
2021-09-22 11:59:50 -07:00
2021-03-13 16:00:09 -08:00
2021-10-03 21:49:19 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-09-10 11:46:28 -07:00
2021-10-03 21:49:21 -07:00
2021-03-13 16:00:09 -08:00
2021-04-27 16:31:39 +09:00
2021-07-28 13:17:58 -07:00
2021-03-13 16:00:09 -08:00
2021-04-08 13:23:25 -07: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
2021-07-26 12:01:26 -07:00
2021-08-24 15:33:23 -07:00
2021-09-10 11:46:30 -07:00
2021-09-23 13:44:48 -07:00
2021-09-23 13:44:48 -07:00
2021-07-28 13:17:59 -07:00
2021-07-22 13:35:20 -07:00
2021-09-28 13:06:53 -07:00
2021-05-04 12:09:43 +09:00
2021-09-20 15:20:43 -07:00
2021-09-20 15:20:43 -07:00
2021-09-10 11:46:27 -07:00
2021-05-04 11:52:02 +09:00
2021-05-04 11:52:02 +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://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%