From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Write Access to buildroot?
Date: Sun, 26 Jul 2009 07:49:48 +0200 [thread overview]
Message-ID: <4A6BEE7C.4080308@atmel.com> (raw)
In-Reply-To: <20090724224516.15b39e30@surf>
Thomas Petazzoni skrev:
> Le Fri, 24 Jul 2009 17:16:30 +0200,
> Ulf Samuelsson <ulf.samuelsson@atmel.com> a ?crit :
>
>
>> And what I am missing, is a way to have several people commit to the
>> same tree.
>> I.E: A development tree.
>>
>
> This is not how development works with Git. Everyone works in its
> own working tree, and asks the project maintainer to pull the working
> tree when things are ready. Things gets integrated in the project
> maintainer tree, which everyone can update from to get the changes from
> the other developers.
>
In the openembedded project all the developers have
write access to the development tree and can create
their own branches within the tree.
This makes it a lot easier to test other peoples patches.
If you look at the statistics for the user repositories,
you see that there are 5 people with user repositories,
including mine, and last updates were from
correa: 3 months ago,
wberrier: 2 months ago,
tpetazzoni: 9 days ago
ulf: 33 hours ago
jacmet: -
This does not indicate a high level of popularity to me.
Maybe people are keeping trees in other locations, but
that means that they are hidden from most users.
In reality, the way Buildroot works today seems to be that
people are sending patches to the mailing-list.
It is fairly easy to set up common git trees,
by creating a "common" user with a git subdirectory
and then have a symbolic link in each user directory
to this git directory with group write permissions.
> In Buildroot, there's no ? development tree ? in the current
> development model. The same tree (the official way) is sometimes a
> development tree (before -rc1 is released), sometimes a stabilization
> tree (between the release of -rc1 and the release of the stable
> version).
>
>
The suggestion does not change this.
> Sincerly,
>
> Thomas
>
BR
Ulf Samuelsson
next prev parent reply other threads:[~2009-07-26 5:49 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 [this message]
2009-07-26 7:15 ` Peter Korsgaard
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=4A6BEE7C.4080308@atmel.com \
--to=ulf.samuelsson@atmel.com \
--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