[Buildroot] Write Access to buildroot?
marc at tensilica.com
Sun Jul 26 20:48:14 UTC 2009
For what it's worth, we have a shared git tree on linux-xtensa.org
for Xtensa arch development of buildroot (we've had it there for
many months before the buildroot project itself switched over to git).
We had to be careful with file ownership/protection (and maybe umask)
to make sure it works smoothly, but once setup, it works quite well.
Everybody has their own userid, no shared user or anything.
We always use the git+ssh://... method to access the tree if we want
to be able to write to it, else anyone can access it read-only using
the usual git://... method -- if you're curious, see:
One also has to be careful to only push things to this tree.
No playing directly with the tree (such as rebase or otherwise
pointing HEAD backwards in time and possibly committing new changes
from there) which plays havoc with others' clones of the tree.
As long as it's only accessed remotely, this is pretty easy.
In case you notice it out of sync... we've only merged this tree with
the official buildroot tree once in a long while -- were waiting for
the Xtensa arch port to get submitted (which it just has, yeah! :-) and
to setup things to make it easier to catch merges that break things.
Ulf Samuelsson wrote:
> Peter Korsgaard skrev:
> >>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson at atmel.com> writes:
> > Hi,
> > >> We also don't want to require outsiders to learn git in order to
> > >> contribute patches.
> > >>
> > Ulf> It it very different to require people to learn git, from
> > Ulf> blocking people that wants to use git, to work together.
> > Blocking? Noone is blocking anyone from anything. That
> particular work
> > flow is not used for the official tree, but you can do what you want
> > to with your own trees.
> I have requested a capability where multiple people have
> write capability to a tree which can then be pulled
> to the official tree.
> It is possible to do this on another git server,
> but that means that it is less visible to other Buildroot users.
> It is simple to implement.
> Create the "common" user, and let developers have
> write access to "~common/git", possibly using a symbolic link.
> > Don't confuse working together with commit access. The Linux kernel
> > gets contributions from ~1000 people for each release, and yet Linus
> > is the only one having commit access to the official tree.
> That comments is irrelevant because I am not asking for commit
> access to the official tree.
> Ulf Samuelsson
> buildroot mailing list
> buildroot at busybox.net
More information about the buildroot