This branch is needed in order to build the Eclipse plugin or else the build will fail when it tries to switch to origin/rocko for yocto-docs. The repo in question: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
Brian, I don't get this Brian... Should I tag the commit in the repo now that to coincide with the commit last used by the engineers when 2.4 M4 froze, which I think was the 19th of September? Problem is there are tons of doc changes yet to be pushed that have to do with 2.4. I usually have that extra month after the M4 freeze to continue working. For past releases, I have not tagged the yocto-docs repo until the release happens. That way if someone checks out yocto-docs on that release, they get a more realistic set of files for the release. Development of the code usually locks down too early for me. I will get this tagged soon. Thanks, Scott
What Brian needs is a rocko branch in the yocto-docs repo. I've created this based on master, it can just track master until the docs diverge between rocko and 2.5. We can continue to add changes to master and rocko, just keeping them updated in parallel ("git push origin master:rocko" updates the rocko branch with master's changes.
Richard, Thanks for tagging it. I could have done that but was unsure of whether or not to do it. Thanks for the instruction on Git as well to keep both branches in sync for the time being. Scott