Comment #4 on issue 340 by chrisbr...@googlemail.com: Migrate away from
Google Code?:
https://code.google.com/p/vim/issues/detail?id=340
Issue 348 has been merged into this issue.
--
You received this message because this project is configured to send all
issue notifications to this addres
Comment #3 on issue 340 by chrisbr...@googlemail.com: Migrate away from
Google Code?:
https://code.google.com/p/vim/issues/detail?id=340
Issue 341 has been merged into this issue.
--
You received this message because this project is configured to send all
issue notifications to this addres
Updates:
Status: Invalid
Comment #2 on issue 340 by chrisbr...@googlemail.com: Migrate away from
Google Code?:
https://code.google.com/p/vim/issues/detail?id=340
Please raise your points at the vim-dev mailinglist as this issue is
discussed there currently. I am going to close this
Comment #1 on issue 340 by sw...@ingo-karkat.de: Migrate away from Google
Code?:
https://code.google.com/p/vim/issues/detail?id=340
This is already being discussed on the vim_dev mailing list
(https://groups.google.com/d/msg/vim_dev/ehzfCDccmek/PU1sTZNdsTUJ); please
join in there and dele
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 340 by universe...@gmail.com: Migrate away from Google Code?:
https://code.google.com/p/vim/issues/detail?id=340
Google code is going to be shut down in January 2016, and will turn
read-only in August 2015 [1].
I suggest m
