From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Write Access to buildroot?
Date: Fri, 24 Jul 2009 17:16:30 +0200 [thread overview]
Message-ID: <4A69D04E.9040408@atmel.com> (raw)
In-Reply-To: <20090724152448.4d1f5934@surf>
Thomas Petazzoni skrev:
> [ Keeping the list in Cc: since these things should probably be
> discussed publicly. ]
>
> Le Fri, 24 Jul 2009 13:37:01 +0200,
> Ulf Samuelsson <ulf.samuelsson@atmel.com> a ?crit :
>
>
>> With read access only, allowing you to make your own tree from the
>> main tree.
>> If you want to share your stuff, before committing to the main tree,
>> you have to do it outside the buildroot world.
>> Am I missing something?
>>
>
> Yes you're missing something.
>
> Look at http://git.buildroot.net/
>
> You have a link to the official Buildroot Git tree, browsable at
> http://git.buildroot.net/buildroot/. This Git tree is read-only, except
> for Peter.
>
> But at the bottom of the page, you have ? User repositories ?. These
> are read/write for their owner. For example, mine is
> http://git.buildroot.net/~tpetazzoni/git/buildroot/. In my own
> repository, I have a master branch which is just a clone of the main
> Buildroot repository. And all the other branches (presently
> directfb-bump, ext-toolchain-target-path, external-toolchain,
> kconfig-update and xorg) contain my *own* work, ready for submission to
> Peter. And some of this work has actually already been integrated in
> mainline (branches directfb-bump, ext-toolchain-target-path and
> external-toolchain).
>
> The link
> http://lists.busybox.net/pipermail/buildroot/2009-March/026875.html
> that I've already posted explains how to use these user repositories,
> that *are read/write.
>
> Does that clarify the situation ?
>
>
And what I am missing, is a way to have several people commit to the
same tree.
I.E: A development tree.
> Sincerly,
>
> Thomas
>
BR
Ulf Samuelsson
next prev parent reply other threads:[~2009-07-24 15:16 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 [this message]
2009-07-24 20:45 ` Thomas Petazzoni
2009-07-26 5:49 ` Ulf Samuelsson
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=4A69D04E.9040408@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