From mboxrd@z Thu Jan 1 00:00:00 1970 From: Markus Heidelberg Date: Wed, 29 Apr 2009 23:00:40 +0200 Subject: [Buildroot] misc development news In-Reply-To: References: <87d4d4md5o.fsf@macbook.be.48ers.dk> <878wlkfp84.fsf@macbook.be.48ers.dk> Message-ID: <200904292300.40446.markus.heidelberg@web.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Thiago A. Corr?a, 29.04.2009: > Hi Peter, > > 2009/4/28 Peter Korsgaard : > > > In fact I would like us to move to a workflow where all changes are > > first posted to the list before committing to the official tree, > > similar to how it's handled in the Linux kernel, U-Boot, ?.. > > I don't see that working. It does for the linux kernel because of the > size of it's contributor base, we are greatly under powered for this > scheme. Patches would just get a big backlog for you to handle and we > would be unable to help. > I think the current commit first review later works best in our case. > We don't quite have enough ppl reviewing changes and reverting a patch > has been uncommon, yet, it's not that hard when necessary. Peter seems to review many commits and fixes them or asks the committers to fix them. So maybe the work isn't really less nowadays, but I'm not sure. > > We had various problems in the past with the svn "ghetto" style of > > development where all developers could commit as they pleased with > > very little review. The git setup works for projects much larger than > > ours, so I think it's atleast worth a try. > > I think the problem was with people management and how we did (or > actually didn't do) conflict solving. In the past we didn't have a > maintainer to help solving the conflicts. > We are not going to really solve it with a different tool. The problems don't have to be solved, because they don't exist any more, at least not in this amount. Markus