<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>I currently don’t understand anything of what is happening on <a href="http://git.centos.org">git.centos.org</a>. Seems far too complicated for me.</div><div><br></div><div>I don’t understand why a « rhel7 » branch does not exist… I think it would be simpler for everyone. Red Hat would simply put new sources on that branch, then CentOS developers would merge it with c7.</div><div><br></div><div>And it would certainly help to shut down this stupid controversy about « Red Hat taking the control of CentOS ».</div><div><br></div><div>Guillaume Derval.</div><div><br></div><div><div><div><div>Le 24 juin 2014 à 20:24, R P Herrold <<a href="mailto:herrold@owlriver.com">herrold@owlriver.com</a>> a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><fieldset style="padding-top: 10px; border: 3px solid rgb(204, 204, 204); padding-left: 20px; position: static; z-index: auto;"><legend style="font-weight:bold">Signé partie PGP</legend><div style="padding-left:3px;">On Tue, 24 Jun 2014, Johnny Hughes wrote:<br><br>> > Will the 'as dropped' kernel and each intermediate kernel<br>> > discussed by upstream in a RHSA, etc be published?<span class="Apple-converted-space"> </span> What is<br>> > the plan as to anaconda integration?<br><br>> So that means we can build both kernels from git ... one to put onto the<br>> iso, the other one (now two after we apply the same changes to the new<br>> kernel-3.10.0-123.4.2.el7)<br>><br>> These kind of changes will only happen when Red Hat imports 2 versions<br>> in before we have a chance to modify the first version ... which will<br>> only likely happen on point releases?<br><br>It is of course a black box to outsiders as to WHO is making<br>such commits into the <a href="http://git.centos.org">git.centos.org</a> image, when they are all<br>mashed together without commit history.<span class="Apple-converted-space"> </span> The 'initial drop'<br>seemingly was from another git, but eliding all commit<br>comments and differentiation as to who the committer was, date<br>of same, etc.<br><br>One assumes RHT Release Engineering and others inside RHT have<br>commit rights on that tree ... the trick in understanding the<br>security model and ability to dis-aggregate who committed what<br>without history<br><br>It was clearly not, as some have opined, a simply unroll of<br>SRPMs and import, as there are several packages with no spec<br>file present.<span class="Apple-converted-space"> </span> List in the file:<br><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/herrold/tool-tips/blob/master/clefos/fixup-dist.sh">https://github.com/herrold/tool-tips/blob/master/clefos/fixup-dist.sh</a><br>in the second 'HERE' document.<span class="Apple-converted-space"> </span> The first outlines spec files<br>needing dist tagfixup<br><br>How does one obtain commits in the centos 'git' tree?<span class="Apple-converted-space"> </span> I<br>understand the model at Github, and am of course well willing<br>to receive pull requests<br><br>-- Russ herrold<br></div></fieldset><br>_______________________________________________<br>CentOS-devel mailing list<br><a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a><br>http://lists.centos.org/mailman/listinfo/centos-devel<br></blockquote></div><br></div></div></body></html>