vim and git

[Nico Weber]

Hi all,

everytime I do some hacking on vim, I put my modified files into a
local svn repository -- which is a bit cumbersome. I found this
article today: http://live.gnome.org/GitForGnomeDevelopers This
sounds as it could be very useful to other people working on vim as
well.

Nico

[Edward L. Fox]

Hi Nico,

I don't think Bram can migrating to git. We had tried to persuade him
to switch to svn but he refused. I just suggest you using svk. It can
make your current situation better.

By the way, some files within the version control will be modified if
you compile Vim in your local working directory. They are always a
major trouble to me. Many developers complained for many times, trying
to persuade Bram to remove those files out of the version control
system, but they did no help at all. That it.

>
> Nico
>
> >
>

Regards,

Edward L. Fox

[Nico Weber]

> I don't think Bram can migrating to git. We had tried to persuade him
> to switch to svn but he refused. I just suggest you using svk. It can
> make your current situation better.
>
> By the way, some files within the version control will be modified if
> you compile Vim in your local working directory. They are always a
> major trouble to me. Many developers complained for many times, trying
> to persuade Bram to remove those files out of the version control
> system, but they did no help at all. That it.

I'm not saying vim should use git. The linked article describes how
you can build a local git repo from an existing svn repo, how to sync
it to svn updates every now and then, and how to use the git repo to
create patches that you can email to this list. It doesn't require
any changes for Bram (there's a svn repository already), it's just
something that might be useful to other people. I'm sure you can tell
git to ignore config.h and friends when generating patches too.

Nico

[Mike Williams]

I've started using Mercury (http://www.selenic.com/mercurial/wiki/) and
its patch queues for developing patches. I have a source repo with the
base source and patches applied and a clone for doing the build (custom
.hgignore and build script added as local patches). Then I have a clone
for each patch worked on. Its quick and easy.

Why Hq and not git? Lousy Win32 support with git.

Mike
--
If cars evolved at the same rate as computers have, they'd cost a fiver,
run for a year on a half-gallon of petrol, and explode once a day.

[Edward L. Fox]

Hi Nico,

On 9/20/07, Nico Weber <nicola...@gmx.de> wrote:

> [...]

>
> I'm not saying vim should use git. The linked article describes how
> you can build a local git repo from an existing svn repo, how to sync
> it to svn updates every now and then, and how to use the git repo to
> create patches that you can email to this list. It doesn't require
> any changes for Bram (there's a svn repository already), it's just
> something that might be useful to other people. I'm sure you can tell
> git to ignore config.h and friends when generating patches too.

I'm terribly sorry for misunderstanding your previous post. Yes, git
is a very powerful tool, but currently only available under Linux (I
don't know whether it can run under FreeBSD now). And the user will
have to learn another set of commands. I think SVK may be a better
choice in such situation because most of its commands are identical to
SVN. And their repository format are all the same. So I can easily
build up a WebSVN right upon my SVK repository.

>
> Nico
>
>
> >
>

Best regards,

Edward L. Fox