Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Write Access to buildroot?
Date: Sun, 26 Jul 2009 09:15:40 +0200	[thread overview]
Message-ID: <87r5w3syn7.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4A6BEE7C.4080308@atmel.com> (Ulf Samuelsson's message of "Sun\, 26 Jul 2009 07\:49\:48 +0200")

>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:

Hi,

 Ulf> In the openembedded project all the developers have
 Ulf> write access to the development tree and can create
 Ulf> their own branches within the tree.

 Ulf> This makes it a lot easier to test other peoples patches.

I don't agree, typing git add remove <foo> is trivial. That's the
glory of the distributed nature of git.

 Ulf> If you look at the statistics for the user repositories,
 Ulf> you see that there are 5 people with user repositories,
 Ulf> including mine, and last updates were from

 Ulf> correa:          3 months ago,
 Ulf> wberrier:       2 months ago,
 Ulf> tpetazzoni:   9 days ago
 Ulf> ulf:                 33 hours ago
 Ulf> jacmet:         -

which corresponds pretty nicely with the list of active developers:

git shortlog -s -n 2009.05..
    73  Peter Korsgaard
    31  Thomas Petazzoni
     9  Maxim Grigoriev
     8  Will Newton
     7  Sven Neumann
     5  Gustavo Zacarias
     4  Nigel Kukard
     2  Bernhard Reutner-Fischer
     2  Daniel Mack
     2  Ulf Samuelsson
     1  Alex Dobrynin
     1  Evan Zelkowitz
     1  H Hartley Sweeten
     1  Lionel Landwerlin
     1  Markus Heidelberg
     1  Pwalters
     1  laurent laffont

Bernhard has his repo on repo.or.cz for historical reasons.

 Ulf> This does not indicate a high level of popularity to me.
 Ulf> Maybe people are keeping trees in other locations, but
 Ulf> that means that they are hidden from most users.

No, it indicates that buildroot is a small project with limited amount
of active developers (and luckily a lot of outside contributers).

 Ulf> In reality, the way Buildroot works today seems to be that
 Ulf> people are sending patches to the mailing-list.

And that's exactly what they should do. We *WANT* to see the patches
on the mailing list so they can get reviewed.

We also don't want to require outsiders to learn git in order to
contribute patches.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-07-26  7:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23 16:40 [Buildroot] Write Access to buildroot? Ulf Samuelsson
2009-07-24  7:54 ` Peter Korsgaard
2009-07-24  8:43   ` Ulf Samuelsson
2009-07-24  8:56     ` Daniel Mack
2009-07-24  9:00       ` Thomas Petazzoni
2009-07-24  9:19       ` Ulf Samuelsson
2009-07-24 10:16         ` Thomas Petazzoni
     [not found]           ` <4A699CDD.7060703@atmel.com>
2009-07-24 13:24             ` Thomas Petazzoni
2009-07-24 15:16               ` Ulf Samuelsson
2009-07-24 20:45                 ` Thomas Petazzoni
2009-07-26  5:49                   ` Ulf Samuelsson
2009-07-26  7:15                     ` Peter Korsgaard [this message]
2009-07-26  9:38                       ` Ulf Samuelsson
2009-07-26 11:53                         ` Peter Korsgaard
2009-07-26 20:21                           ` Ulf Samuelsson
2009-07-26 20:34                             ` Peter Korsgaard
2009-07-26 20:48                             ` Marc Gauthier
2009-07-27  6:40                               ` Ulf Samuelsson
2009-07-27  7:45                                 ` Thomas Petazzoni
2009-07-27  6:59                               ` Ulf Samuelsson
2009-07-27  7:38                             ` Thomas Petazzoni
2009-07-24 13:09     ` Peter Korsgaard
     [not found]       ` <4A69D246.9060206@atmel.com>
2009-07-25  6:52         ` Peter Korsgaard

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=87r5w3syn7.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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