I do have two branches (master and Bernard) in my yocto-docs contrib area. The master branch is used for updates to the upcoming release and is in various states of correctness/completeness. I guess I will need to take the time to do a push for every change I make to my local copy of yocto-docs master.
The docs that are on the website are Bernard only until we release. ScottR -----Original Message----- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Richard Purdie Sent: Thursday, July 14, 2011 4:15 PM To: Robert P. J. Day Cc: yocto@yoctoproject.org Subject: Re: [yocto] why does quick start guide refer to non-provided "poky-image-sato"? On Thu, 2011-07-14 at 19:10 -0400, Robert P. J. Day wrote: > On Thu, 14 Jul 2011, Joshua Lock wrote: > > > As I understand it documentation repository updates are reflected on > > the website so the docs tend to reflect the released version. > > > > It would be nice to be able to provide development & release > > documentation but I can't see it happening any time soon. > > ok, that explains it but it doesn't defend it. IMHO, any single > versioned tarball or repository checkout should always be internally > consistent, and that includes embedded documentation. when i do a > "git pull" of any software, i expect the contents of any docs/ > directory to reflect what's there. > > if you want to publicly publish the docs that reflect the last > official release, then build those docs from the appropriate git tag. I agree that the docs in master should reflect the code in master and that the docs on the bernard branch should be the ones which make the bernard references. Which or both can end up on the website as needed which is a separate issue. I thought this had been fixed and Scott had two branches so what's going wrong? :/ Cheers, Richard _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
