On Fri, Mar 09, 2018 at 10:33:22PM +0000, Grant Likely wrote: > On Thu, Mar 8, 2018 at 2:00 AM, David Gibson <david@xxxxxxxxxxxxxxxxxxxxx> > wrote: > > On Wed, Mar 07, 2018 at 06:20:34PM +0000, Grant Likely wrote: > >> Hi folks, > >> > >> Anyone object to me adding a fork of dtc to the devicetree-org GitHub > >> page? I'd like to start running the dtc CI loop in TravisCI, and that > >> is dead easy for projects in GitHub. > > > > As Frank said, I already have a dtc tree on github, > > https://github.com/dgibson/dtc > > and it's already wired up to Travis at: > > https://travis-ci.org/dgibson/dtc/branches > > > > It's generally in sync with the kernel.org tree (my normal workflow is > > push to github, check the Travis build succeeded, then push to > > kernel.org). > > > > I don't have a strong objection to having another copy under > > devicetree-org, but I'm not sure if it accomplishes anything extra. > > > >> Or, should we just straight out move dtc to GitHub? > > > > I'd prefer not to do that. > > The main reason for having a copy on the DT.org github page is to give it a > higher profile repo with accompanying CI status badge. Out of curiosity, > what are your reasons for not wanting to move it to the dt.org page? Sorry, I should clarify. I don't have any objection to putting it on the dt.org github page and advertising that. I just don't want that to become the only / primary site for the repository. One reason is that I don't think we should remove / change an existing widely advertised repo unless there's a rather more compelling reason to. Another is that I'd prefer not to rely on a commercial supplier whose interests may not match ours, particularly not when we already have other hosting set up. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Attachment:
signature.asc
Description: PGP signature
