High Markus!
On 2015-04-01 Wednesday at 08:50 +0300 LCD 47 wrote: > On 1 April 2015, Markus Heidelberg <[email protected]> wrote: > > if switching to Git, we could seriously consider cleaning up the > > repository, now it might be the last chance for quite a while. > > > > I have collected some possibilities for improvement - some simple, > > some a bit more complicated, but if found the proper commands/scripts, > > the automated tasks should work without much hassle. > [...] > This is a very well thought-out list, +1. +1 Until now in the vim project mercurial is used just for deployment of vim versions. The many possibilities to save workload are _not yet_ used. Instead, a significant effort is made to separate the runtime part -- I fail to see any benefit of this separation, I see only troubles and additional workload caused by this separation: patches split over multiple commits, patches not sufficient for building vim. Thank you Markus! Based on your work, after a well thought _one-time_ effort, we can use git as a tool, which _saves_ workload for Bram and everybody else involved, rather than to add workload. Most interesting: Bram gets the option to automate _completely_ the management of the todo list by usage of git. The todo list can become autogenerated by git, initially in part, and some day completely: • Another git branch can correspond to every entry in the todolist, just a useful scheme for the names of this “todo” and “work in progress” branches is needed. If Bram prefers mails or pull requests for submitting of patches does not matter, both ways are possible, the latter probably with less workload for him: he could use just “git pull” or “git am”. And if the commit author field needs adjustment because the full name of the author is missing in the mail From: header, there is “git commit --amend”. git itself and many other small and large software projects are managed with such a workflow -- probably with good reasons. • This way git can tie together reliably the names of the original patch author and other contributors, multiple versions of patches, the changeset the patches are based on, and an arbitrary number of comments (a git commit can contain a message without a patch). Todo list entries can get a unique identity -- no need any more to search them in mailboxes, no more erroneous assignments of patches. Other contributors can test patches easier. • When Bram decides to include a patch in the master branch, he just merges the regarding branch, solves merge conflicts sometimes, runs “make test“ sometimes, and adds his improvements and final polish. This last step is important for the success of vim and could become more visible (optionally separate commits), we could learn more easily from Brams expertise. I imagine, this can save so much workload for Bram, that the todo list can start to shrink, rather than to grow for ever .. an exciting vision :) -- Roland Eggner -- -- 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 subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
pgpEhIGbhzPrb.pgp
Description: PGP signature
