This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
The GCC project allows anyone with write privileges to create branches in the CVS repository for aribtrary purposes, provided that the usual guidelines regarding copyrights are followed. A typical use of these branches is for distributors to created branches to use for releases, or for developers to perform experiments. It's an effective way of making more information available to people without getting in the way of the mainline development.
Does the same policy apply to GLIBC and/or Binutils? If not, could it be considered?
I don't think that the binutils group has ever developed a plan for branches. I don't think anybody has ever wanted to make a binutils branch other than the ones we make for releases.
Personally I think it is perfectly reasonable to follow the gcc approach: anybody with write privileges can create a branch, but all commits to that branch require a copyright assignment just as with all commits to mainline.
Nick, Alan, any thoughts on this?
Cheers Nick
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |