merge(3p/git): Merge git upstream at v2.26.2
This commit is contained in:
commit
5229c9b232
1006 changed files with 149006 additions and 60819 deletions
17
third_party/git/Documentation/git-gc.txt
vendored
17
third_party/git/Documentation/git-gc.txt
vendored
|
|
@ -115,15 +115,14 @@ NOTES
|
|||
-----
|
||||
|
||||
'git gc' tries very hard not to delete objects that are referenced
|
||||
anywhere in your repository. In
|
||||
particular, it will keep not only objects referenced by your current set
|
||||
of branches and tags, but also objects referenced by the index,
|
||||
remote-tracking branches, refs saved by 'git filter-branch' in
|
||||
refs/original/, reflogs (which may reference commits in branches
|
||||
that were later amended or rewound), and anything else in the refs/* namespace.
|
||||
If you are expecting some objects to be deleted and they aren't, check
|
||||
all of those locations and decide whether it makes sense in your case to
|
||||
remove those references.
|
||||
anywhere in your repository. In particular, it will keep not only
|
||||
objects referenced by your current set of branches and tags, but also
|
||||
objects referenced by the index, remote-tracking branches, notes saved
|
||||
by 'git notes' under refs/notes/, reflogs (which may reference commits
|
||||
in branches that were later amended or rewound), and anything else in
|
||||
the refs/* namespace. If you are expecting some objects to be deleted
|
||||
and they aren't, check all of those locations and decide whether it
|
||||
makes sense in your case to remove those references.
|
||||
|
||||
On the other hand, when 'git gc' runs concurrently with another process,
|
||||
there is a risk of it deleting an object that the other process is using
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue