Hi Christian, 2016/1/28 Thu 5:32:52 UTC+9 Christian Brabandt wrote: > Hi Bram! > > On Mi, 27 Jan 2016, Bram Moolenaar wrote: > > > > > Christian Brabandt wrote: > > > > > On Sa, 23 Jan 2016, Ken Takata wrote: > > > > > > > > If Bram creates this sub-repository, I can create the daily upload > > > > > script. However I am not sure yet, how this is supposed to work. Am I > > > > > right, that in theory, we'd only need to run the upate-repo.sh script > > > > > once per day? > > > > > > > > Yes, run the update-repo.sh in the following way once per day: > > > > > > > > cd /path/to/local-repository > > > > ./scripts/update-repo.sh > > > > > > > > Or: > > > > > > > > /path/to/local-repository/scripts/update-repo.sh > > > > /path/to/local-repository > > > > > > > > > > > > Of cause, when running the script, the "origin" of git setting must > > > > point > > > > the new repository under the vim org. > > > > > > Thanks Ken, this is really helpful. > > > > > > I cloned from your repository and created > > > https://github.com/chrisbra/vim-win32-installer > > > It will run daily and hopefully create new Windows binaries and upload > > > them to https://github.com/chrisbra/vim-win32-installer/releases > > > > > > That seems to work so far. I slightly adjusted the documentation and the > > > commit messages.
Thank you. The commit messages look pretty good now! > > > If this works well enough for the next time, I think we can move the > > > repository to github.com/vim/vim > > > > I think you mean github.com/vim/vim-win32-installer > > Yes. > > > > (I hope the appveyor deploy key then still works, we will have to find > > > out.) > > > > I'm not sure exactly how to do this, it should be possible to move a > > repository from an individual to an organisation. Can't find it in the > > github help. > > Yes, it is possible to transfer ownship. I think it is in the settings > section below dangerous somewhere. However, one needs to create a secret > key for appveyor to enable it to push back to github. I am not sure, > whether with the current key appveyor will be able to push back to > github/vim/vim-win32-installer In my understanding, the key is bound to your account. So if you have write permission to vim/vim-win32-installer, the current key can be used. > I guess we see, once I transfered ownership and you pushed the next > patches. I can do that whenever you want. Is there a time, you like the > cronjob to run, just in case it fails (like yesterday) and you want to > fix that one fast? Currently, it will try to syn on midnight. Now I can see the vim/vim-win32-installer repository. I can see the latest tag v7.4.1187, but the build is not started. I suppose it was because of the GitHub server trouble. I hope that clicking "NEW BUILD" button on appveyor goes fine. Regards, Ken Takata -- -- 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.
