Daniel Hahler wrote:
> in the process of moving the repository to Github I suggest using the
> existing mirror from https://github.com/vim-jp/vim as a starting
> point.
>
> This would make it easier for existing patches / pull requests (based
> on this AFAIK most popular Git mirror) to get integrated into Vim
> itself later, because of the then common history.
>
> Additionally it would make it easier/trivial for users that are using
> this mirror to migrate to Vim's new repository.
I suppose that after the migration tool has done its work, we can
replace the repository with another one. For me it doesn't matter, so
long as at some point I can commit changes to github (like I have been
doing the last few weeks). I suppose it would be as simple as cloning
the vim-jp repository, I pull it and continue work from there.
As Christian asked: How does the cleanup script fit in?
It's best to have a step-by-step description of what should happen to
avoid ending up with something that isn't what we want.
Keep in mind I'm not a git user.
--
Managers are like cats in a litter box. They instinctively shuffle things
around to conceal what they've done.
(Scott Adams - The Dilbert principle)
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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.
