My First Object Walk
-2024-02-08 +2024-02-12Reviewing Patches in the Git Project
-2024-02-08 +2024-02-12Submitting Patches
-2024-02-08 +2024-02-12Tools for developing Git
-2024-02-08 +2024-02-12Everyday Git With 20 Commands Or So
-2024-02-08 +2024-02-12DESCRIPTION
on the subcommand:git bisect start [--term-(new|bad)=<term-new> --term-(old|good)=<term-old>]
+git bisect start [--term-(bad|new)=<term-new> --term-(good|old)=<term-old>]
[--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<pathspec>...]
git bisect (bad|new|<term-new>) [<rev>]
git bisect (good|old|<term-old>) [<rev>...]
-git bisect terms [--term-good | --term-bad]
+git bisect terms [--term-(good|old) | --term-(bad|new)]
git bisect skip [(<rev>|<range>)...]
git bisect reset [<commit>]
git bisect (visualize|view)
@@ -887,8 +887,10 @@ Alternate terms
git bisect terms
You can get just the old (respectively new) term with git bisect terms
---term-old
or git bisect terms --term-good
.
You can get just the old term with git bisect terms --term-old
+or git bisect terms --term-good
; git bisect terms --term-new
+and git bisect terms --term-bad
can be used to learn how to call
+the commits more recent than the sought change.
If you would like to use your own terms instead of "bad"/"good" or
"new"/"old", you can choose any names you like (except existing bisect
subcommands like reset
, start
, …) by starting the
@@ -1244,7 +1246,7 @@
GIT
diff --git a/git-bisect.txt b/git-bisect.txt index 8e01f1d61..82f944dc0 100644 --- a/git-bisect.txt +++ b/git-bisect.txt @@ -16,11 +16,11 @@ DESCRIPTION The command takes various subcommands, and different options depending on the subcommand: - git bisect start [--term-(new|bad)=Variables
walking fewer objects. +
+pack.allowPackReuse=multi
may improve the time it takes to create a pack by
+reusing objects from multiple packs instead of just one.
+
FIELD NAMES
In any case, a field name that refers to a field inapplicable to the object referred by the ref does not cause an error. It returns an empty string instead.
As a special case for the date-type fields, you may specify a format for
-the date by adding :
followed by date format name (see the
-values the --date
option to git-rev-list(1) takes).
As a special case for the date-type fields, you may specify a format for the
+date by adding :
followed by date format name (see the values the --date
+option to git-rev-list(1) takes). If this formatting is provided in
+a --sort
key, references will be sorted according to the byte-value of the
+formatted string rather than the numeric value of the underlying timestamp.
Some atoms like %(align) and %(if) always require a matching %(end). We call them "opening atoms" and sometimes denote them as %($open).
When a scripting language specific quoting is in effect, everything @@ -1497,7 +1499,7 @@
GIT
diff --git a/git-for-each-ref.txt b/git-for-each-ref.txt index be9543f68..3a9ad91b7 100644 --- a/git-for-each-ref.txt +++ b/git-for-each-ref.txt @@ -359,9 +359,11 @@ In any case, a field name that refers to a field inapplicable to the object referred by the ref does not cause an error. It returns an empty string instead. -As a special case for the date-type fields, you may specify a format for -the date by adding `:` followed by date format name (see the -values the `--date` option to linkgit:git-rev-list[1] takes). +As a special case for the date-type fields, you may specify a format for the +date by adding `:` followed by date format name (see the values the `--date` +option to linkgit:git-rev-list[1] takes). If this formatting is provided in +a `--sort` key, references will be sorted according to the byte-value of the +formatted string rather than the numeric value of the underlying timestamp. Some atoms like %(align) and %(if) always require a matching %(end). We call them "opening atoms" and sometimes denote them as %($open). diff --git a/git-remote-helpers.html b/git-remote-helpers.html index 2a9ce39b0..ab705c782 100644 --- a/git-remote-helpers.html +++ b/git-remote-helpers.html @@ -735,7 +735,7 @@git-remote-helpers
-2024-02-08 +2024-02-12Keep authoritative canonical history correct with git pull
-2024-02-08 +2024-02-12Keep authoritative canonical history correct with git pull
diff --git a/howto/maintain-git.html b/howto/maintain-git.html index 330b0a1d5..85df96133 100644 --- a/howto/maintain-git.html +++ b/howto/maintain-git.html @@ -735,7 +735,7 @@How to maintain Git
-2024-02-08 +2024-02-12Preparing a "merge-fix"
diff --git a/howto/new-command.html b/howto/new-command.html index eab435ae0..bc32559fe 100644 --- a/howto/new-command.html +++ b/howto/new-command.html @@ -735,7 +735,7 @@How to integrate new subcommands
-2024-02-08 +2024-02-12Integrating a command
diff --git a/howto/rebase-from-internal-branch.html b/howto/rebase-from-internal-branch.html index 78ca75820..72580ad92 100644 --- a/howto/rebase-from-internal-branch.html +++ b/howto/rebase-from-internal-branch.html @@ -735,7 +735,7 @@How to rebase from an internal branch
-2024-02-08 +2024-02-12How to rebase from an internal branch
diff --git a/howto/rebuild-from-update-hook.html b/howto/rebuild-from-update-hook.html index 5c3fd5d9f..6dc9321ef 100644 --- a/howto/rebuild-from-update-hook.html +++ b/howto/rebuild-from-update-hook.html @@ -735,7 +735,7 @@How to rebuild from update hook
-2024-02-08 +2024-02-12How to rebuild from update hook
diff --git a/howto/recover-corrupted-blob-object.html b/howto/recover-corrupted-blob-object.html index bf20bbdc8..f577659fa 100644 --- a/howto/recover-corrupted-blob-object.html +++ b/howto/recover-corrupted-blob-object.html @@ -735,7 +735,7 @@How to recover a corrupted blob object
-2024-02-08 +2024-02-12How to recover a corrupted blob object
diff --git a/howto/recover-corrupted-object-harder.html b/howto/recover-corrupted-object-harder.html index 312f57310..433f07680 100644 --- a/howto/recover-corrupted-object-harder.html +++ b/howto/recover-corrupted-object-harder.html @@ -735,7 +735,7 @@How to recover an object from scratch
-2024-02-08 +2024-02-12The adventure continues…
diff --git a/howto/revert-a-faulty-merge.html b/howto/revert-a-faulty-merge.html index 3ef57b4c0..069021538 100644 --- a/howto/revert-a-faulty-merge.html +++ b/howto/revert-a-faulty-merge.html @@ -735,7 +735,7 @@How to revert a faulty merge
-2024-02-08 +2024-02-12How to revert a faulty merge
diff --git a/howto/revert-branch-rebase.html b/howto/revert-branch-rebase.html index 195050101..19638e291 100644 --- a/howto/revert-branch-rebase.html +++ b/howto/revert-branch-rebase.html @@ -735,7 +735,7 @@How to revert an existing commit
-2024-02-08 +2024-02-12How to revert an existing commit
diff --git a/howto/separating-topic-branches.html b/howto/separating-topic-branches.html index 415284956..dffce4750 100644 --- a/howto/separating-topic-branches.html +++ b/howto/separating-topic-branches.html @@ -735,7 +735,7 @@How to separate topic branches
-2024-02-08 +2024-02-12How to separate topic branches
diff --git a/howto/setup-git-server-over-http.html b/howto/setup-git-server-over-http.html index 2abe0240c..f05fa1c2b 100644 --- a/howto/setup-git-server-over-http.html +++ b/howto/setup-git-server-over-http.html @@ -735,7 +735,7 @@How to setup Git server over http
-2024-02-08 +2024-02-12Troubleshooting:
diff --git a/howto/update-hook-example.html b/howto/update-hook-example.html index 23df62a86..f91f36f6b 100644 --- a/howto/update-hook-example.html +++ b/howto/update-hook-example.html @@ -735,7 +735,7 @@How to use the update hook
-2024-02-08 +2024-02-12How to use the update hook
diff --git a/howto/use-git-daemon.html b/howto/use-git-daemon.html index c98d935d6..0cc269cb4 100644 --- a/howto/use-git-daemon.html +++ b/howto/use-git-daemon.html @@ -735,7 +735,7 @@How to use git-daemon
-2024-02-08 +2024-02-12How to use git-daemon
diff --git a/howto/using-merge-subtree.html b/howto/using-merge-subtree.html index c1a337ed8..465e607eb 100644 --- a/howto/using-merge-subtree.html +++ b/howto/using-merge-subtree.html @@ -735,7 +735,7 @@How to use the subtree merge strategy
-2024-02-08 +2024-02-12Additional tips
diff --git a/howto/using-signed-tag-in-pull-request.html b/howto/using-signed-tag-in-pull-request.html index 55c04d33e..caa02766f 100644 --- a/howto/using-signed-tag-in-pull-request.html +++ b/howto/using-signed-tag-in-pull-request.html @@ -735,7 +735,7 @@How to use a signed tag in pull requests
-2024-02-08 +2024-02-12Auditors
diff --git a/technical/api-error-handling.html b/technical/api-error-handling.html index a4f079324..f5b81d99e 100644 --- a/technical/api-error-handling.html +++ b/technical/api-error-handling.html @@ -735,7 +735,7 @@Error reporting in git
-2024-02-08 +2024-02-12Git API Documents
-2024-02-08 +2024-02-12merge API
-2024-02-08 +2024-02-12parse-options API
-2024-02-08 +2024-02-12Simple-IPC API
-2024-02-08 +2024-02-12Trace2 API
-2024-02-08 +2024-02-12GIT bitmap v1 format
-2024-02-08 +2024-02-12Bundle URIs
-2024-02-08 +2024-02-12Git hash function transition
-2024-02-08 +2024-02-12Long-running process protocol
-2024-02-08 +2024-02-12Multi-Pack-Index (MIDX) Design Notes
-2024-02-08 +2024-02-12Concerning Git’s Packing Heuristics
-2024-02-08 +2024-02-12Parallel Checkout Design Notes
-2024-02-08 +2024-02-12Partial Clone Design Notes
-2024-02-08 +2024-02-12Use of index and Racy Git problem
-2024-02-08 +2024-02-12Scalar
-2024-02-08 +2024-02-12Git-send-pack internals
-2024-02-08 +2024-02-12Shallow commits
-2024-02-08 +2024-02-12Trivial merge rules
-2024-02-08 +2024-02-12Unit Testing
-2024-02-08 +2024-02-12Table of Contents
- Introduction
- 1. Repositories and Branches
- How to get a Git repository
- How to check out a different version of a project
- Understanding History: Commits
- Manipulating branches
- Examining an old version without creating a new branch
- Examining branches from a remote repository
- Naming branches, tags, and other references
- Updating a repository with git fetch
- Fetching branches from other repositories
- 2. Exploring Git history
- 3. Developing with Git
- 4. Sharing development with others
- 5. Rewriting history and maintaining patch series
- 6. Advanced branch management
- 7. Git concepts
- 8. Submodules
- 9. Low-level Git operations
- 10. Hacking Git
- 11. Git Glossary
- A. Git Quick Reference
- B. Notes and todo list for this manual
Git is a fast distributed revision control system.
This manual is designed to be readable by someone with basic UNIX +
Table of Contents
- Introduction
- 1. Repositories and Branches
- How to get a Git repository
- How to check out a different version of a project
- Understanding History: Commits
- Manipulating branches
- Examining an old version without creating a new branch
- Examining branches from a remote repository
- Naming branches, tags, and other references
- Updating a repository with git fetch
- Fetching branches from other repositories
- 2. Exploring Git history
- 3. Developing with Git
- 4. Sharing development with others
- 5. Rewriting history and maintaining patch series
- 6. Advanced branch management
- 7. Git concepts
- 8. Submodules
- 9. Low-level Git operations
- 10. Hacking Git
- 11. Git Glossary
- A. Git Quick Reference
- B. Notes and todo list for this manual
Git is a fast distributed revision control system.
This manual is designed to be readable by someone with basic UNIX command-line skills, but no previous knowledge of Git.
Chapter 1, Repositories and Branches and Chapter 2, Exploring Git history explain how to fetch and study a project using git—read these chapters to learn how to build and test a particular version of a software project, search for