| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>
|
|
|
|
| |
Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>
|
|
|
|
|
|
|
| |
We have to do this every time we cut a release branch. The
non-numeric milestone RELEASE will now start to be used for any FIXME
or TODO that needs doing when the release branch gets cut for a
versioned documentation build.
|
|
|
|
| |
Thanks to forum user AndyH for the suggestion.
|
|
|
|
| |
Thanks to forum user AndyH for the corrections.
|
|
|
|
|
| |
This is a pretty brain-dead way to manage these pre-release
preparations. Should figure out the done thing and use that instead.
|
|
|
|
|
|
|
| |
In line with some changes made earlier today to the maple-ide repo,
the master libmaple branch no longer points to a particular IDE
release as "current", since there's no way it can know. From now on,
only release branches will contain the blessed download links.
|
| |
|
|
|
|
|
| |
Merging in the standalone refactor docs, etc. The individual libmaple
API pages are going to need to get redone.
|
| |
|
|
|
|
|
|
|
| |
Simplified and clarified "flashing your own bootloader" documentation.
Also made Windows 7 IDE workaround link directly to the forum post
with the workaround, instead of the start of the thread.
|
|
|
|
| |
Maple hardware and design files. Other tweaks and improvements.
|
| |
|
| |
|
| |
|
|
|