<meta content="text/html; charset=ISO-8859-1"
<body text="#000000" bgcolor="#FFFFFF">
Absolutely. It's no problem for us to create public repo on github
for example. Actually we already did. You can find it here
<meta http-equiv="content-type" content="text/html;
. All the work will be pushed here over time.<br>
Have a nice day.<br>
On 09/30/2013 08:57 PM, Greg Troxel wrote:<br>
<blockquote cite="mid:firstname.lastname@example.org" type="cite">
(I haven't been reading quagga mail the last week or so, and just stuck
my head in, so sorry if I'm missing context.)
With git, preparing changes, and administrative issues of write
permission are decoupled. So if your group has a public repository
forked from savannah, where master is origin/master, and there's a
feature.eigrp branch or something, then everyone can just add it as a
remote and fetch and review and try your changes. When the time
comes and the mailinglist concurs the code is ready, David or I can
merge and push.
(I'm not clear on the details of granting write access on savannah, and
in general people having write access and preparing branches is quite
Does this make sense?