Am Freitag, 14. August 2015, 20:38:49 schrieb Bram Moolenaar: > > Markus Heidelberg wrote: > > > > > Oh, I just noticed, of course we cannot just use a new git > > > > repository/project on GitHub, otherwise the issues are gone. > > > > The final official repository has to be pushed to one created by the > > > > Google exporter therefore. > > > > > > For the one that's there now I created the repository on github and then > > > pushed the locally converted repo to there. Is there something wrong > > > with it, compared to using the one created by the Google exporter? > > > So far I thought it would be fine, so long as the name ends up being the > > > same. > > > > The name does not matter. The current vim/vim repository does not > > contain the issues exported from Google Code, they reside in > > vim/vim-old-tryout as well as the single pull request. They move with > > the rename of the repository/project. > > Oh, the issues are on the repository, not on the project. I see.
I guess you mean "organization" instead of "project" here, github.com/vim in this case. The projects (vim/vim or vim/vim-old-tryout) each contain their own repository and issue database. > Well, I didn't see them, since issues were disabled in settings. > > I didn't get your remark "the issues are gone", I was thinking of > repository issues, not Vim issues. > > Hmm, one can add a repository and delete a repository, but making it > totally empty and pushing a fresh repo into it appears not to be > possible. > > So, is the conclusion that we need to push the cleaned-up Mercurial > repository to Google code before doing the export? No, that doesn't make a difference. You can remove outdated branches and tags from the Git repository via "git push" and overwrite the master branch by force-pushing. As Matthew already wrote, you just have to make sure to delete anything you don't overwrite. Since there are so many tags, it is best to just delete them all. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
