[Buildroot] Write Access to buildroot?

Ulf Samuelsson ulf.samuelsson at atmel.com
Fri Jul 24 09:19:36 UTC 2009

> On Fri, Jul 24, 2009 at 10:43:06AM +0200, Ulf Samuelsson wrote:
>> > http://lists.busybox.net/pipermail/buildroot/2009-March/026875.html
>> >
>> > and
>> >
>> > http://buildroot.net/git.html
>> >
>> >
>> OK,
>> Have not been active for a while and have about 3000 unread emails.
>> Seems to me that there a multiple people with write access
>> from the git commit mails, How come?
> That's just the git post-commit hook that takes the original author as
> sender address of the email. That always happens when Peter picks a
> patch and commits it to his tree.
>> Personally, I think it would make sense to have
>> a development git with personal branches with write access.
>> This would complement any personal git's and would allow
>> easier testing with other people's patches.
> The thing about git and other distributed SCMs is: everbody has write
> access. To his local copy. You can than push your tree to an publically
> accesible external tree and share your personal patches with others.

That is the problem, buildroot does not provide a "publically accesible 
external tree"
for developers.
Why rely on github.com mentioned below which people won't find on their own?

If the development tree is within buildroot, then people are more likely to 
test it
or contribute.

> Or do the same thing by sending a thread of patches, if you don't want
> to share your patches among others before they're ready for the master
> branch.
>> The main tree, used for the release
>> could then pull changes from both the development tree
>> and the personal tree's.
> This is basicaly exactly the same thing than having your own repository,
> with the difference that the admins of ublibc.org won't have to fiddle
> with user permissions.

The difference is that the development tree is shared.

>> Is there a list of maintainers?
>> The target/device/Atmel tree will need to be updated due to the 
>> SAM9G10/G45/M10/M11.
>> The target/linux tree is also in need of maintenance.
> That's exactly why you want to have distributed repositories. You simply
> don't have to care about all that. Once you tested the patches in your
> tree for long enough, simply send in a pull request, and they will end
> up in the master branch.
> There a multiple free git hosting services out there, for example
> github.com.

Thanks for the link.

> Hope that helps :)
> Daniel

Best Regards
Ulf Samuelsson                ulf at atmel.com
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavallerivägen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57

More information about the buildroot mailing list