One of the repository malformations most likely to confuse
reposurgeon's attempt to create a git DAG is a branch delete followed
by a branch copy with the same target name. Because of this, I
have reposurgeon throw a warning whenever it sees a mid-branch
delete.
The Wesnoth repo has these:
mid-branch delete: on refs/heads/utbs at commit@266118=<31003>
mid-branch delete: on tags/1.1.8 at commit@94237=<12797>
mid-branch delete: on refs/heads/fendrin_editor at commit@365874=<42097>
mid-branch delete: on refs/heads/shadowmaster_filesystem at
commit@208957=<24491>
mid-branch delete: on tags/1.1.7 at commit@89598=<12196>
mid-branch delete: on refs/heads/fendrin_pathfind at commit@356044=<40927>
mid-branch delete: on tags/1.0.1 at commit@54520=<8618>
mid-branch delete: on tags/1.1.7 at commit@89999=<12230>
mid-branch delete: on tags/1.1.3 at commit@85202=<11605>
I'm guessing some of these branches are obsolete and can be removed.
The more of them I can get rid of, the less likely I am to trip over
a problem that will require tricky surgery. Also, any branches we
can discard help shrink the repository, which is presently over
GitHub's size limit.
Which of these can be deleted?
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
The most foolish mistake we could possibly make would be to permit
the conquered Eastern peoples to have arms. History teaches that all
conquerors who have allowed their subject races to carry arms have
prepared their own downfall by doing so.
-- Adolph Hitler, April 11 1942.
_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev
