search for: nvie

...how version control is used in Dovecot development, which should help avoid these kind of problems. The main problem now is that everything gets directly committed to the master branch (although we have a separate more stable dovecot-ee repo also). The new plan is to do something like this: http://nvie.com/posts/a-successful-git-branching-model/ Besides some minor compiling issues and other small changes, the important ones are: - director: Login UNIX sockets were normally detected as doveadm or director ring sockets, causing it to break in existing installations. - sdbox: When copying a m...

...how version control is used in Dovecot development, which should help avoid these kind of problems. The main problem now is that everything gets directly committed to the master branch (although we have a separate more stable dovecot-ee repo also). The new plan is to do something like this: http://nvie.com/posts/a-successful-git-branching-model/ Besides some minor compiling issues and other small changes, the important ones are: - director: Login UNIX sockets were normally detected as doveadm or director ring sockets, causing it to break in existing installations. - sdbox: When copying a m...

...is a git tool named "git-flow" that specifically supports this model and it seems like it might fit the LLVM development model so I wanted to point it out in case others had not seen it. Perhaps the more core developers can comment more on its usefulness in the LLVM ecosystem. [1] http://nvie.com/posts/a-successful-git-branching-model/ [2] http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/ -- Wesley Peck University of Kansas SLDG Laboratory On Jul 23, 2011, at 3:16 PM, FlyLanguage wrote: >>> Yes, but who's mainline? Is the plan to have a centralized repo with...

>> Yes, but who's mainline? Is the plan to have a centralized repo with a mainline branch that everybody pushes to > > This one. > >> , or the a linux style model where some person has an official mainline to which he pulls? > > Not this one. > > This shouldn't be a mysterious concept, our policies are well documented here: >

...t;git-flow" that specifically supports this model > and it seems like it might fit the LLVM development model so I wanted to > point it out in case others had not seen it. Perhaps the more core > developers can comment more on its usefulness in the LLVM ecosystem. > > [1] http://nvie.com/posts/a-successful-git-branching-model/ > [2] http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/ > > I was reading through the thread and was going to post a link to the same blog post when I came across yours. While I have not use 'git flow', I have used the same b...

On Jul 23, 2011, at 5:37 AM, FlyLanguage wrote: >>>> After git, mainline will still be the most important branch for >>>> the *project*, >>>> but you will work with quite a few branches on parallel. >>>> >>>> >>>> Who's mainline? :) Be prepared to assign a super-merger, like Linus, >>>> to maintain

Hi, As part of the migration of LLVM's source code to github, we need to update our developer policy with instructions about how to interact with the new git repository. There are a lot of different topics we will need to discuss, but I would like to start by initiating a discussion about our merge commit policy. Should we: 1. Disallow merge commits and enforce a linear history by

I''m looking for a bit of best-practices here. Our puppet environment up-until-today has been owned and operated by IT Operations only. We''ve had a single ''production'' environment and our code has been managed in a local GitHub::FI install. We have ~14,000 lines of code in our PP files. We''re trying to make two changes to our environment... that may need