summaryrefslogtreecommitdiff
path: root/t/t5506-remote-groups.sh
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2018-04-29 00:44:44 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-04-30 11:12:31 +0900
commitf9f99b3f7d06716336b239bcf122eb5a7348bfd5 (patch)
tree2a7813e7ae8389cfef632073f4d5f654a53bfef7 /t/t5506-remote-groups.sh
parentAdd a test for `git replace --convert-graft-file` (diff)
downloadtgif-f9f99b3f7d06716336b239bcf122eb5a7348bfd5.tar.xz
Deprecate support for .git/info/grafts
The grafts feature was a convenient way to "stitch together" ancient history to the fresh start of linux.git. Its implementation is, however, not up to Git's standards, as there are too many ways where it can lead to surprising and unwelcome behavior. For example, when pushing from a repository with active grafts, it is possible to miss commits that have been "grafted out", resulting in a broken state on the other side. Also, the grafts feature is limited to "rewriting" commits' list of parents, it cannot replace anything else. The much younger feature implemented as `git replace` set out to remedy those limitations and dangerous bugs. Seeing as `git replace` is pretty mature by now (since 4228e8bc98 (replace: add --graft option, 2014-07-19) it can perform the graft file's duties), it is time to deprecate support for the graft file, and to retire it eventually. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Reviewed-by: Stefan Beller <sbeller@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5506-remote-groups.sh')
0 files changed, 0 insertions, 0 deletions