> > 2) We just use sf.net for committing. That is if esr eventually manages > to get > the conversion done we would then (no idea how yet) move all commits done > over > to the github repo. > This is simply a matter of remembering the last commit before the conversion (tags can help here) and running git format-patch before_conv..master afterwards to generate a series of patches. git am can then apply those patches (including commit metadata!) to the new repositoriy.
3) We just move over what we have right now at st.net to github and start > working there. > Shadowmaster already uploaded an exact mirror of the sourceforge repo on github as 'wesnoth-test'. If we want to wait for the conversion to finish, we can just use that. 4) We already have something at github but I know that some branches in > there > are probably not working as intended. No idea what the status of that part > is > *exactly* compared to the repo at sf.net. > The 'wesnoth' repo on github seems to contain the master branch and all tags. A normal git clone will get the master and the tags on that branch (so all development releases plus occasionally the first stable tag). git fetch --all doesn't fetch anything else, but git fetch --tags does fetch all tags (including, say, 1.10.6). I'm currently running a git clone --mirror to get some more information on this, but AFAICT all the branch references (besides master) are missing (but the commit objects themselves might be present).
_______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
