Patrick Steinhardt <ps@xxxxxx> writes: > The grafting mechanism for objects has been deprecated in e650d0643b > (docs: mark info/grafts as outdated, 2014-03-05), which is more than a > decade ago. The mechanism can lead to hard-to-debug issues and has a > superior replacement with replace refs. > > Follow through with the deprecation and mark grafts for removal in Git > 3.0. > > Signed-off-by: Patrick Steinhardt <ps@xxxxxx> > --- > Documentation/BreakingChanges.txt | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > > diff --git a/Documentation/BreakingChanges.txt b/Documentation/BreakingChanges.txt > index 5d7e80aebb..9fb6d8c78a 100644 > --- a/Documentation/BreakingChanges.txt > +++ b/Documentation/BreakingChanges.txt > @@ -96,6 +96,18 @@ Cf. <2f5de416-04ba-c23d-1e0b-83bb655829a7@xxxxxxxxxxx>, > > === Removals > > +* Support for grafting commits has long been superseded by git-replace(1). > + Grafts are inferior to replacement refs: > ++ > + ** Grafts are a local-only mechanism and cannot be shared across reositories. "reositories" -> "repositories". > + ** Grafts can lead to hard-to-diagnose problems when transferring objects > + between repositories. > ++ > +The grafting mechanism has been marked as outdated since e650d0643b (docs: mark > +info/grafts as outdated, 2014-03-05) and will be removed. > ++ > +Cf. <20140304174806.GA11561@xxxxxxxxxxxxxxxxxxxxx>. > + > == Superseded features that will not be deprecated > > Some features have gained newer replacements that aim to improve the design in