On Thu, Jun 26, 2008 at 1:46 AM, John Beckett <[EMAIL PROTECTED]> wrote: > I use the FTP server to get patches (with a Python script - very easy), and I > apply > them manually (easy). So I have no personal interest in the CVS or SVN > distributions. However, lurking here has shown quite a bit of pain associated > with > them, so I would be glad if something could be done to:
I also track vim-dev by usually doing this: downloading the patches, and seldom use CVS/SVN. The biggest trouble I see is I need to format patches/suggestions in the same way, if I do not have write commit access. > > 1. Make life easier for Bram. -and- If you see how Bram is handling (well) vim, it has a linear development. No branches, No merge. When he moves on to the next release, the previous one does not get updated patches (it seldom happens). So actually Bram could do the whole maintainance of vim by just using git-gui (graphical interface tcl/tk based). At this stage, it is so much easier than any of the competing tools. It is a fact. I intend to re-build a clean git tree for vim (don't expect it sooner than next week). I will be able to show graphically why it would be easy to maintain vim with git. > 2. Reliably update CVS and SVN for those that want them > (or be so superior that CVS/SVN will be abandonded). > > IMHO any suggestions need to outline what Bram would do (to illustrate (1)), > and > what a user would do (to illustrate (2)). If these two hurdles are passed, the > question of reliability can be investigated. It is superior and can update cvs/svn trees accordingly too. > > I cannot see how using wget to download patches as above, or downloading the > whole > tree, would be an improvement for a user. being able to download a snapshot without having to apply all patches ourselves can be quite a time saver, no ? -- Christian -- http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside ! --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
