Saluton Marc :)

Marc Weber <[email protected]> dixit:
> Excerpts from Raúl Núñez de Arenas Coronado's message of Sat Jul 18 19:35:19 
> +0200 2009:
>> For me, saving time for Bram is enough.
> Doesn't git solve all these problems in the nicest way possible?

Not at all unless Bram puts time explaining which revisions are
"inter-patches" (so, probably unstable and you shouldn't try to build
Vim from them) and which revisions are not.

In the end, he should maintain two public branches: one for unstable
code, another for stable code. Right now he has probably his revision
control private and publishes only code that can be considered stable.

I do more or less the same with my projects. I have Bazaar branches for
all of them containing the current development code, and from time to
time I publish stable versions. I don't want nor like to maintain a
stable branch and do merges from the unstable branch. Way too much work
for me. If anyone wants to play with the code, he can branch from my
repositories, no problem. But I don't release new versions or patches
from a Bazaar branch. My view.

> And it's not only about Bram's time. It's a about everyone's time trying
> playing around with the code and new features.

Then ask Bram to publish his repositories.

> If you like I can write down a short introduction to top-git showing
> why it's a great collaborative tool to keep patches (and their merges)
> up to date.

Thanks, but no thanks. I'm very happy with Bazaar, and I don't decide
about Vim sources, repositories and whatnot. You have to ask Bram, not
me. I was just explaining why I think Bram doesn't publish a tarball
containing patches from 001 to latest. I wasn't even discussing revision
control systems ;)

-- 
Raúl "DervishD" Núñez de Arenas Coronado
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to