Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Heidelberg <markus.heidelberg@web.de>
To: buildroot@busybox.net
Subject: [Buildroot] misc development news
Date: Wed, 29 Apr 2009 23:00:40 +0200	[thread overview]
Message-ID: <200904292300.40446.markus.heidelberg@web.de> (raw)
In-Reply-To: <d6cda7730904290758r250060del52fa1fbafad25474@mail.gmail.com>

Thiago A. Corr?a, 29.04.2009:
> Hi Peter,
> 
> 2009/4/28 Peter Korsgaard <jacmet@uclibc.org>:
> 
> > 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

  reply	other threads:[~2009-04-29 21:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27  9:39 [Buildroot] misc development news Peter Korsgaard
2009-02-27 22:05 ` Markus Heidelberg
2009-02-27 23:09   ` Peter Korsgaard
2009-03-31 21:23 ` Peter Korsgaard
2009-04-01  4:47   ` Thiago A. Corrêa
2009-04-28 21:22     ` Peter Korsgaard
2009-04-29 14:58       ` Thiago A. Corrêa
2009-04-29 21:00         ` Markus Heidelberg [this message]
2009-04-29 21:17           ` Thiago A. Corrêa
2009-05-01 18:57             ` Markus Heidelberg
2009-04-30 14:03           ` Peter Korsgaard
2009-05-01 19:03             ` Markus Heidelberg
2009-04-30 13:50         ` Peter Korsgaard
2009-04-06  0:22   ` Thomas Petazzoni
2009-04-06  7:45     ` Peter Korsgaard
2009-04-29  9:44   ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2009-04-06 17:13 Darcy Watkins
     [not found] <mailman.6835.1239009687.25474.buildroot@busybox.net>
2009-04-06 19:01 ` Frank Hoeflich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200904292300.40446.markus.heidelberg@web.de \
    --to=markus.heidelberg@web.de \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox