On Thu, Sep 16, 2021 at 1:37 AM Paul Koning via Gcc <gcc@gcc.gnu.org> wrote: > > > > > On Sep 15, 2021, at 5:21 PM, Joseph Myers <jos...@codesourcery.com> wrote: > > > > On Wed, 15 Sep 2021, Paul Koning via Gcc wrote: > > > >> Some questions about developer branches: > >> > >> 1. Who may create one? Who may write to them? > >> 2. Are they required to be listed in https://gcc.gnu.org/git.html ? I > >> notice it mentioned a whole pile of them, most of which don't seem to > >> exist. > > > > A devel/ branch (one in refs/heads/devel/) is a shared development branch, > > which may be created by anyone with write access (who can decide how it > > will work in terms of patch approvals etc.), should be documented in > > git.html, and will not accept non-fast-forward pushes or branch deletion. > > > > A user branch (in refs/users/<username>/heads/) is a personal development > > branch, which may be created by that user (sourceware username), may not > > necessarily be documented in git.html, and can have non-fast-forward > > pushes or branch deletion (it's up to that user to decide the rules for > > that branch, including for non-fast-forward pushes). Likewise a vendor > > branch (in refs/vendors/<vendor>/heads/). > > > > All branches are subject to the same legal requirements (copyright > > assignment or DCO for code committed there). > > ... > > Thanks, that's useful. Suppose I want to collaborate with one other person > (for now) on pdp11 target work, does it make sense to keep that in a user > branch since the community is so small and isolated? I assume the other > person would need (as a minimum) write-after-approval privs.
Note another option is to host int on github or gitlab and base it off their mirrors of the GCC repo. Without write-after-approval access the person would not be able to push to the repo at gcc.gnu.org but of course you could do this with changes sent by mail for example. Richard. > > paul >
