• N
    receive-pack: allow pushes that update .git/shallow · 0a1bc12b
    Nguyễn Thái Ngọc Duy 提交于
    The basic 8 steps to update .git/shallow does not fully apply here
    because the user may choose to accept just a few refs (while fetch
    always accepts all refs). The steps are modified a bit.
    
    1-6. same as before. After calling assign_shallow_commits_to_refs at
       step 6, each shallow commit has a bitmap that marks all refs that
       require it.
    
    7. mark all "ours" shallow commits that are reachable from any
       refs. We will need to do the original step 7 on them later.
    
    8. go over all shallow commit bitmaps, mark refs that require new
       shallow commits.
    
    9. setup a strict temporary shallow file to plug all the holes, even
       if it may cut some of our history short. This file is used by all
       hooks. The hooks could use --shallow-file=$GIT_DIR/shallow to
       overcome this and reach everything in current repo.
    
    10. go over the new refs one by one. For each ref, do the reachability
       test if it needs a shallow commit on the list from step 7. Remove
       it if it's reachable from our refs. Gather all required shallow
       commits, run check_everything_connected() with the new ref, then
       install them to .git/shallow.
    
    This mode is disabled by default and can be turned on with
    receive.shallowupdate
    Signed-off-by: NNguyễn Thái Ngọc Duy <pclouds@gmail.com>
    Signed-off-by: NJunio C Hamano <gitster@pobox.com>
    0a1bc12b
commit.h 10.2 KB