Johannes Schindelin <johannes.schinde...@gmx.de> writes:
> On Fri, 13 Apr 2018, Jakub Narebski wrote:
>> Hallvard Breien Furuseth <h.b.furus...@usit.uio.no> writes:
>>> Also maybe it'll be worthwhile to generate .git/info/grafts in a local
>>> clone of the repo to get back easily visible history. No grafts in
>>> the original repo, grafts mess things up.
>> Just a reminder: modern Git has "git replace", a modern and safe
>> alternative to the grafts file.
> Maybe it is time to start deprecating grafts? They *do* cause problems,
> such as weird "missing objects" problems when trying to fetch into, or
> push from, a repository with grafts. These problems are not shared by the
> `git replace` method.
Also you can propagate "git replace" info with clone / fetch / push.
> I just sent out a patch to add a deprecation warning.
Thank you for this.