On Thu, Feb 23, 2012 at 9:58 PM, Muneyuki Noguchi <nogu....@gmail.com> wrote: > In many projects, the master branch in Git is used as "trunk" in Subversion. > Branches except for master can be used as "stable branch" in Subversion. > > Changes to doc/RELEASING would be as follows: > > svn export http://uim.googlecode.com/svn/trunk > -> git archive --remote=<url of uim repo> HEAD | tar -xvf - > > svn cp https://uim.googlecode.com/svn/trunk \ > https://uim.googlecode.com/svn/branches/x.y > -> git branch x.y && git push origin x.y > > svn cp https://uim.googlecode.com/svn/branches/x.y \ > https://uim.googlecode.com/svn/tags/uim-x.y.z-alpha > -> git tag -a uim-x.y.z-alpha && git push --tags > > svn export http://uim.googlecode.com/svn/tags/uim-x.y.z-alpha > -> git archive --remote=<url of uim repo> uim-x.y.z-alpha | tar -xvf - > > Changes to sigscheme/doc/release.txt would be similar to ones to > doc/RELEASING.
Thanks for the explanation. >> Also with migrating to git, I think it good timing for you to take a >> maintainer role of uim. >> I think you are the most active developer introducing new things and >> implementations to >> uim currently. Of course I can help you to some extent. Could you >> consider to become a >> maintainer? > > > OK, I will take the role. > Could you set my role in the uim project to "Owner" > for me to change the repository type to Git? Thanks! I've set you as "Owner" of the project. uim 1.7.3 is quite stable now, so please go on the development for uim 1.8 and later. And I hope to see releasing uim 1.8 from you :) > FYI, My migration plan is as follows: > > (1) Convert repositories > Convert 3 repositories from Subversion to Git with svn2git. > > * uim > * sigscheme > * libgcroots > > (2) Add libgcroots as a submodule to sigscheme > > git submodule add <url of libgcroots repo> > > (3) Add sigscheme as a submodule to uim > > git submodule add <url of sigscheme repo> > > (4) Replace `svn co' in make-wc.sh with `git submodule' > > * svn export $SSCM_URL sigscheme > * svn export $LIBGCROOTS_URL sigscheme/libgcroots > -> git submodule update --init --recursive > > (5) Replace `svn export' in make-dist.sh with `git submodule' > > In the uim repository, > * svn export $SSCM_URL sigscheme > * svn export $LIBGCROOTS_URL sigscheme/libgcroots > -> git submodule update --init --recursive > > In the sigscheme repository, > * svn export $LIBGCROOTS_URL libgcroots > -> git submodule update --init > > (6) Update tools/gnuify-changelog.pl to handle `git log' > > See https://gist.github.com/1892559 > > (7) Replace `svn log' in Makefile.am with `git log' > > svn log $(RELEASE_URL) | ./gnuify-changelog.pl > $@ > -> git log $(RELEASE_URL) | ./gnuify-changelog.pl > $@ > > (8) Replace `svn export' in Makefile.am with `git archive' > > svn export $(UIM_REPOSITORY)/trunk/tools/gnuify-changelog.pl > -> git archive --remote=<url of uim repo> HEAD tools/gnuify-changelog.pl -o > gnuify-changelog.pl > > (9) Update RELEASING and sigscheme/doc/release.txt > > I will create a converted Git repository in Google Code > instead of GitHub because no all committer has a GitHub account. > If there is no objection from the contributors, > I will carry out the migration plan this weekend. OK. That's fine for me. Cheers, -- Etsushi Kato -- Google Groups "uim-en" group uim-en@googlegroups.com http://groups.google.com/group/uim-en/about
