Ingo Karkat, 2010-01-16:
> On 16-Jan-2010 17:54, Markus Heidelberg wrote:
> > Ingo Karkat, 2010-01-10:
> >> I would hope that the Mercurial repository will make it easier (i.e. no
> >> manual
> >> import of sent patches, no separate Runtime sync) for Markus to update his
> >> Git
> >> repo.
> >
sc, 2010-01-16:
> On Saturday 16 January 2010 10:54:13 am Markus Heidelberg wrote:
>
> > vim_extended.git is based on vim_mainline so it will not be
> > continued in the same way. One solution would be to use a
> > tool like hg-to-git to import the official repo into a git
> > branch, but I gue
On 16-Jan-2010 17:54, Markus Heidelberg wrote:
Ingo Karkat, 2010-01-10:
I would hope that the Mercurial repository will make it easier (i.e. no manual
import of sent patches, no separate Runtime sync) for Markus to update his Git
repo.
When the Mercurial repository becomes official and Vim fi
On Saturday 16 January 2010 10:54:13 am Markus Heidelberg wrote:
> vim_extended.git is based on vim_mainline so it will not be
> continued in the same way. One solution would be to use a
> tool like hg-to-git to import the official repo into a git
> branch, but I guess a better approach would b
Ingo Karkat, 2010-01-10:
> On 09-Jan-2010 16:46, sc wrote:
> > one voice: i stopped using CVS after i tried markus' git
> > repository with the relative number patch and never looked back
> >
> > he's got the runtime in his too
> >
> I would hope that the Mercurial repository will make it easie
