Skip to content
Commits on Feb 25, 2009
  1. @mickeyl

    Add deprecation notice.

    mickeyl committed Feb 25, 2009
Commits on Feb 24, 2009
  1. @troth @cbrake

    introduction.xml: Fix spelling of Angstrom.

    * Use character entities.
    troth committed with cbrake Feb 23, 2009
Commits on May 9, 2008
  1. @ocampana @leggewie

    common_use_cases.xml: add para to two listitems to fix compilation pr…

    …oblem reported in bug 4233
    
    * commit by Laibsch
    ocampana committed with leggewie May 9, 2008
Commits on Feb 28, 2008
  1. @leggewie
  2. @leggewie

    common_use_cases.xml: correct path to sane-srcrevs.inc. Thanks Junqia…

    …n for spotting the error.
    leggewie committed Feb 28, 2008
Commits on Feb 26, 2008
  1. @leggewie
Commits on Jan 29, 2008
  1. @leggewie
Commits on Jan 7, 2008
  1. @leggewie

    merge of '3b3c3d2924189df3b073018ca4958ca23b85c9ad'

         and '9b35cd745d3158465f0faf0168c235f39441c6f0'
    leggewie committed Jan 7, 2008
  2. @leggewie

    usermanual.xml: sample export command was broken in docu.

    Applying fix from bug 2209. Thanks for spotting it.
    Sorry for the earlier try at fixing that ran into difficulties with the automerger it seems.
    leggewie committed Jan 7, 2008
  3. @leggewie

    merge of '3437f20735d7e47c5e1b66b06048bf07a88dcb10'

         and '6eb0ce0ee03896c04704340de3de39f7b173e851'
    leggewie committed Jan 7, 2008
  4. @leggewie
  5. @leggewie

    usermanual.xml: sample export command was broken in docu.

    Applying fix from bug 2209.  Thanks for spotting it.
    leggewie committed Jan 7, 2008
Commits on Dec 22, 2007
  1. @pfalcon
  2. @pfalcon
  3. @pfalcon
  4. @pfalcon
  5. @pfalcon
  6. @pfalcon

    merge of '338f5fc9c32e401a6033a90c9d909663dc527857'

         and 'a345293c1e1d325c7d86ed713f89778c64f62735'
    pfalcon committed Dec 22, 2007
  7. @pfalcon

    usermanual.xml: Describe OE feed support facilities, FEED_URIS and FE…

    …ED_DEPLOYDIR_BASE_URI.
    pfalcon committed Dec 22, 2007
  8. @pfalcon

    usermanual.xml: Reorder chapters, put Getting Started after Intro.

    * Of course, user-friendly manuals are written like this:
    1. Intro
    2. Easy way
    3. Details
    not like:
    1. Intro
    2. Lotsa dark and morbid knowledge
    3. Now, let's set up it
    pfalcon committed Dec 22, 2007
  9. @pfalcon

    usermanual.xml: Chapter title: "Getting OpenEmbedded" -> "Getting Sta…

    …rted with OpenEmbedded"
    pfalcon committed Dec 22, 2007
  10. @pfalcon
  11. @pfalcon

    usermanual.xml: Update mtn version to 0.29, as this appears to be oldest

    version for which DB snapshot is provided.
    pfalcon committed Dec 22, 2007
  12. @pfalcon
  13. @pfalcon

    usermanual.xml: Fix typos.

    pfalcon committed Dec 22, 2007
Commits on Dec 15, 2007
  1. @pfalcon
  2. @pfalcon

    usermanual.xml: Use easier wording on results of lack of shlibs depen…

    …dency detection
    
    on ASSUME_PROVIDED libs.
    pfalcon committed Dec 15, 2007
Commits on Jul 25, 2007
Commits on Jun 13, 2007
  1. usermanual usage: Add the missing section_id on the configuration cha…

    …pter so
    
    it gets a filename that'll remain constant.
    Jamie Lenehan committed Jun 13, 2007
  2. usermanual: Split each of the original chapters out of usermanual.xml…

    … into a
    
    seperate file per chapter in the chapters subdirectory. In preparation for
    cleaning up some of the overlap between chapters and to make life a bit
    easier for editing and merging.
    Jamie Lenehan committed Jun 13, 2007
  3. usermanual/usage: Add some details on what configuration files exist …

    …in OE.
    Jamie Lenehan committed Jun 13, 2007
Commits on Jun 8, 2007
  1. usermanual: Rename the sample in the recipes chapter from helloworld to

    myhelloworld since someone committed a helloworld recipe to OE and that's
    now where the documentation was saying to put this example.
    Jamie Lenehan committed Jun 8, 2007
Commits on Jun 6, 2007
  1. @leggewie

    usermanual.xml: Replace references to bitbake 1.6 with 1.8.

    The change is a little bit early as 1.8 is not yet officially required.
    But the general consensus in IRC seems to be that whenever somebody
    with a problem pops in that is on 1.6 to just update to 1.8.
    leggewie committed Jun 6, 2007
Something went wrong with that request. Please try again.