On Sun, Dec 10, 2023 at 2:59 AM Junio C Hamano <gitster@xxxxxxxxx> wrote: > Is it a viable option to stick to the name "test-lib" (or possibly, > "git-test-lib" to make it more prominent to say where it came from)? Will rename the project to "git-test-lib". > If you do not plan to coordinate with those who work on (the remnant > of) the original sharness based on an ancient version of our test > framework, and do not plan to actively transition its users to your > version, it is less confusing if you named yours differently, as it > avoids hinting that your version is a successor of theirs. > > I am not sure if reusing the history of our project verbatim using > filter-repo is really a good way to help those who are interested in > the test framework, by the way. If all historical commits were squashed, it would be difficult to track future changes of test-lib in the Git project. Futhermore, who will be the author of the squashed commit? > and unedited filter-repo result will describe such a commit > primarily to explain why the changes in the commit was made on Git > side. Most of the changes described in the resulting commit message > are discarded by filter-repo and the resulting history becomes hard > to follow. One solution is to add notes in the README file and users can refer to the commit history of the git project.
