Add more context to comment

Author: cruessler

gix-blame/tests/blame.rs

@@ -736,9 +736,11 @@ mod baseline {
 /// blamed file as well as in the original file that introduced them. This follows `git`’s
 /// behaviour. `libgit2`, as of 2024-09-19, only checks whether two entries are adjacent in the
 /// blamed file which can result in different blames in certain edge cases. See [the commit][1]
-/// that introduced the extra check into `git` for context.
+/// that introduced the extra check into `git` for context. See [this commit][2] for a way to test
+/// for this behaviour in `git`.
 ///
 /// [1]: https://github.com/git/git/commit/c2ebaa27d63bfb7c50cbbdaba90aee4efdd45d0a
+/// [2]: https://github.com/git/git/commit/6dbf0c7bebd1c71c44d786ebac0f2b3f226a0131
 fn coalesce_blame_entries(lines_blamed: Vec<BlameEntry>) -> Vec<BlameEntry> {
     // TODO
     // It’s possible this could better be done on insertion into `lines_blamed`.