Derrick Stolee 31ad6b61bd branch: add branch_checked_out() helper
The validate_new_branchname() method contains a check to see if a branch
is checked out in any non-bare worktree. This is intended to prevent a
force push that will mess up an existing checkout. This helper is not
suitable to performing just that check, because the method will die()
when the branch is checked out instead of returning an error code.

Create a new branch_checked_out() helper that performs the most basic
form of this check. To ensure we can call branch_checked_out() in a loop
with good performance, do a single preparation step that iterates over
all worktrees and stores their current HEAD branches in a strmap. The
branch_checked_out() helper can then discover these branches using a
hash lookup.

This helper is currently missing some key functionality. Namely: it
doesn't look for active rebases or bisects which mean that the branch is
"checked out" even though HEAD doesn't point to that ref. This
functionality will be added in a coming change.

We could use branch_checked_out() in validate_new_branchname(), but this
missing functionality would be a regression. However, we have no tests
that cover this case!

Add a new test script that will be expanded with these cross-worktree
ref updates. The current tests would still pass if we refactored
validate_new_branchname() to use this version of branch_checked_out().
The next change will fix that functionality and add the proper test
coverage.

Signed-off-by: Derrick Stolee <derrickstolee@github.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-06-15 10:47:18 -07:00
2021-12-15 09:39:49 -08:00
2022-05-20 15:27:00 -07:00
2021-03-13 16:00:09 -08:00
2022-06-15 10:47:18 -07:00
2021-08-12 14:00:52 -07:00
2022-03-29 12:22:02 -07:00
2021-05-07 12:47:41 +09:00
2022-03-09 10:25:27 -08:00
2022-01-07 15:19:34 -08:00
2021-03-13 16:00:09 -08:00
2022-03-30 18:01:10 -07:00
2022-01-05 14:01:28 -08:00
2022-05-10 17:41:10 -07:00
2021-03-13 16:00:09 -08:00
2022-04-20 16:17:35 -07:00
2022-03-28 10:25:52 -07:00
2021-09-23 13:44:48 -07:00
2022-04-11 16:44:45 -07:00
2022-05-05 14:36:37 -07:00
2022-03-13 22:56:17 +00:00
2021-03-13 16:00:09 -08:00
2022-04-06 15:21:59 -07:00
2022-05-02 09:50:37 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2022-05-02 09:50:37 -07:00
2022-01-27 12:07:53 -08:00
2021-03-13 16:00:09 -08:00
2022-05-23 14:39:54 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2022-05-02 09:50:37 -07:00
2021-08-24 15:32:37 -07:00
2022-05-05 14:36:37 -07:00
2022-04-04 10:56:23 -07:00
2021-10-25 16:06:58 -07:00
2022-04-06 09:42:12 -07:00
2022-04-20 16:17:33 -07:00
2022-04-20 16:17:33 -07:00
2022-03-28 10:25:52 -07:00
2022-03-28 10:25:52 -07:00
2022-03-23 14:09:29 -07:00
2021-05-04 11:52:02 +09:00
2021-05-04 11:52:02 +09:00
2022-05-02 09:50:37 -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 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
Git with broken hash generation to generate collisions between object IDs. Don't use this!
https://undefinedbehavior.de/posts/commit-vandalism/
Readme 217 MiB
Languages
C 50%
Shell 38.2%
Perl 5.5%
Tcl 3.5%
Python 0.9%
Other 1.7%