On 8/18/15, Bram Moolenaar wrote:
>
> There were a couple of hiccups, but the repository has moved to GitHub
> now. It's in the destination place: https://github.com/vim/vim
>
> Now we need to do the git cleanup. I'll hold off until it looks OK,
> https://github.com/vim/vim-tryout is what it wou
On 18-Aug-15, Christian Brabandt wrote:
> Here is a documentation update:
>
> Stay with mercurial
> ===
>
> A repository at bitbucket.org has been setup that mirrors the official Vim
> source repository at https://github.com/vim/vim
Minor nit-pick:
"has been setup" -> "has
There were a couple of hiccups, but the repository has moved to GitHub
now. It's in the destination place: https://github.com/vim/vim
Now we need to do the git cleanup. I'll hold off until it looks OK,
https://github.com/vim/vim-tryout is what it would look like.
At least it doesn't have the ol
Am Dienstag, 18. August 2015, 18:42:50 schrieb Bram Moolenaar:
>
> I wrote:
>
> > Applying your git cleanup script after the conversion from hg to git
> > produces lots of these errors:
> >
> > fatal: ambiguous argument 'v7.2.434~4': unknown revision or path not in the
> > working tree.
> > Use
Christian Brabandt wrote:
> On Di, 18 Aug 2015, Bram Moolenaar wrote:
>
> > Note: I have started doing things "for real".
> > The cleaned up Mercurial repository has been pushed to Google code.
>
> I have resynced the bitbucket mirror. I will update the sync script
> tomorrow, when the new gith
On Di, 18 Aug 2015, Bram Moolenaar wrote:
> Note: I have started doing things "for real".
> The cleaned up Mercurial repository has been pushed to Google code.
I have resynced the bitbucket mirror. I will update the sync script
tomorrow, when the new github repository should be available. And onc
You should have mentioned the Hg mirrors too. :)
--
--
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 subscribe
Hello Vim users,
If you never use the Mercurial repository or deal with issues, you can
stop reading now.
Google Code is shutting down, the Vim project is being moved to Github.
While this is happening, no changes are to be made.
Especially, don't add new issues or edit existing issues.
These ch
Note: I have started doing things "for real".
The cleaned up Mercurial repository has been pushed to Google code.
I'll now start the export to github. We can redo this when needed.
In preparation I've renamed the previously exported repo, which was
overwritten with the cleaned up one, to vim-try
On 18 August 2015, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > On 18 August 2015, Bram Moolenaar wrote:
> > [...]
> > > For users who switch from Mercurial on Google Code to the Mercurial
> > > mirror, there would be an extra commit that doesn't exist anywhere
> > > else. I hope that will work.
I wrote:
> Applying your git cleanup script after the conversion from hg to git
> produces lots of these errors:
>
> fatal: ambiguous argument 'v7.2.434~4': unknown revision or path not in the
> working tree.
> Use '--' to separate paths from revisions, like this:
> 'git [...] -- [...]'
>
> I
Lcd wrote:
> On 18 August 2015, Bram Moolenaar wrote:
> [...]
> > For users who switch from Mercurial on Google Code to the Mercurial
> > mirror, there would be an extra commit that doesn't exist anywhere
> > else. I hope that will work.
> [...]
>
> Why not make the Bitbucket mirror at the
Markus -
Applying your git cleanup script after the conversion from hg to git
produces lots of these errors:
fatal: ambiguous argument 'v7.2.434~4': unknown revision or path not in the
working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
I'll have a look my
On 18 August 2015, Bram Moolenaar wrote:
[...]
> For users who switch from Mercurial on Google Code to the Mercurial
> mirror, there would be an extra commit that doesn't exist anywhere
> else. I hope that will work.
[...]
Why not make the Bitbucket mirror at the same time as the Github
migr
Markus Heidelberg wrote:
> > Wonderful! And just in time, I'm working on Vim today.
>
> Then staying up late was worth it :)
And thanks for checking the plan.
> > So, these are the steps to be taken:
> > 1. Stop making changes: "freeze"; announce on Google code project page.
> >Announce o
Am 2015-08-18 14:56, schrieb Markus Heidelberg:
7. Commit a change in the Mercurial repo to break the build, pointing
the user
to github. Do NOT push this yet.
8. Convert the Mercurial repo to github.
9. Commit a change that undoes the build breakage.
10. Run the git cleanup script: ~/tmp/cl
Comment #5 on issue 390 by dbarn...@google.com: "[[2;2R" printed in buffer
area on vim startup
https://code.google.com/p/vim/issues/detail?id=390
I got it to repro again and changing the length checks like #3 above
doesn't seem to have helped.
--
You received this message because this pro
I hope I don't brake the mail chain, I'm not at home at my mail client.
> Wonderful! And just in time, I'm working on Vim today.
Then staying up late was worth it :)
> So, these are the steps to be taken:
> 1. Stop making changes: "freeze"; announce on Google code project page.
>Announce on
Patch 7.4.827
Problem:Not all test targets are in the Makefile.
Solution: Add the missing targets.
Files: src/Makefile
*** ../vim-7.4.826/src/Makefile 2015-06-21 13:44:07.297340941 +0200
--- src/Makefile2015-08-18 13:45:09.538267948 +0200
***
*** 1902,1925
---
Markus Heidelberg wrote:
> Am Sonntag, 16. August 2015, 15:23:15 schrieb Bram Moolenaar:
> >
> > OK, if there is a chance you still find some improvements for the
> > Mercurial cleanup, we better wait a bit before doing that.
> >
> > Once you have it all figured out, I hope you can send me the
Roland Eggner wrote:
> Hi Bram
> Hi Christian
[...]
> > The example is missing the pipe symbol
>
> Good catch. Bram dropped the 2nd example I proposed in my patch.
>
>
> I attached 2 variants of a new patch covering both issues. They differ only
> regarding the 2nd issue:
> (1) re-adds my
Am Sonntag, 16. August 2015, 15:23:15 schrieb Bram Moolenaar:
>
> OK, if there is a chance you still find some improvements for the
> Mercurial cleanup, we better wait a bit before doing that.
>
> Once you have it all figured out, I hope you can send me the final
> scripts. I wouldn't want some
22 matches
Mail list logo
