This is the mail archive of the mailing list for the GDB 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]

Re: git is live

> > GCC has always allowed vendor branches.  I don't see any reason that
> > binutils/gdb should prohibit them.  Obviously all the code has to be
> > under the GPL or some other explicitly permitted license.
> I believe the GCC policy is that the code must also be assigned to the
> FSF, just as it would be for trunk.

Outside of the policy, I am starting to rethink the policy of
allowing vendor branches. For centralized version control systems
such as SVN, it makes sense, because there is no other choice.

But for decentralized systems such as git, I think vendor branches
could be just as easily hosted elsewhere.  With git, it's really easy
for anyone to host it somewhere, and publish its location. It's also
equally easy for anyone interested in the work to add that location
a remote, and fetch from it.

We could allow exceptions on a case-by-case basis; for instance
we'd allow it if some contributor was constrained by his employer.

But otherwise, everyone who uses the default "fetch" ends up
fetching everything, including vendor branches that they are
not interested in.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]