diff options
| author | Douwe Maan <douwe@gitlab.com> | 2016-09-05 10:48:06 +0000 |
|---|---|---|
| committer | Douwe Maan <douwe@gitlab.com> | 2016-09-05 10:48:06 +0000 |
| commit | ae1da08f25e6253c1d58ac24214a63572bf533db (patch) | |
| tree | ada9567479dc93c1f494930bc0d9b68fe053ab54 /db | |
| parent | b46c703b841c78a8c7616d320fc3e85ed645fab1 (diff) | |
| parent | ffef94f17e16a9ca9f0c1d1b970f2354d5144357 (diff) | |
| download | gitlab-ce-ae1da08f25e6253c1d58ac24214a63572bf533db.tar.gz | |
Merge branch 'safe-ref-updates' into 'master'
Safer ref updates
Use `git update-ref` to prevent clobbering concurrent ref updates. If
rugged/libgit2 is temporarily confused, due to concurrent `git gc` for
example, then it used to be possible to accidentally reset a ref to an
earlier state and lose commits. Because `git update-ref` does not get
confused by `git gc`, what will happen now is that the commit based on
confused information fails, preventing data loss.
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/20353
See merge request !6130
Diffstat (limited to 'db')
0 files changed, 0 insertions, 0 deletions