On Monday 13 January 2014 03:13:14 I wrote:
> What is the current situation of the Git repository conversion? Supposedly,
> the current repository needs fixing some things, which is why we ended up
> with the "wesnoth-old" name on GitHub last April. Is this still being
> worked on?
I went and dug up the relevant ML posts [1] [2].
1: https://mail.gna.org/public/wesnoth-dev/2013-04/msg00024.html
2: https://mail.gna.org/public/wesnoth-dev/2013-04/msg00025.html
>From ESR's post [1]:
* (1) could be easily fixed with git filter-branch or reposurgeon
* (2) appears to be commit 97d9aefdd166ab61260cbffa63ead04651e7c844. Any
others?
* (3) appears to be commits 909cbdb59ca2737c5f80f5c913c29913c59ebf2a and
a072e54e12de0e7a6445d60e241a860aa4f277b9.
>From AI0867's post [2]:
* What I said above for (1) from ESR's post applies to this too.
All in all, I still don't feel this warrants another full repository rewrite.
We could just document the errata in a wiki page (or even a file in the
repository itself), forget about the issues forever, and rename
wesnoth/wesnoth-old to wesnoth/wesnoth to save everyone the inconvenience of
having to explain what the "-old" suffix stands for every once in a while.
What do you think?
--
Regards
Ignacio R. Morelle <shadowm>
P.S.: Sorry for the exclamation signs, but I doubt anyone will reply to or
even *read* this post otherwise, if the activity in this thread so far is any
indication.
_______________________________________________
Wesnoth-dev mailing list
Wesnoth-dev@gna.org
https://mail.gna.org/listinfo/wesnoth-dev
