Skip to content

gnrc: enhance documentation#4415

Merged
miri64 merged 3 commits intoRIOT-OS:masterfrom
cgundogan:pr/gnrc/doc
Dec 9, 2015
Merged

gnrc: enhance documentation#4415
miri64 merged 3 commits intoRIOT-OS:masterfrom
cgundogan:pr/gnrc/doc

Conversation

@cgundogan
Copy link
Copy Markdown
Member

This PR includes a preliminary version of gnrc's documentation. However, much more info can be added to that. @authmillenon can you add more info where you think it's necessary?

@cgundogan cgundogan added Area: network Area: Networking Area: doc Area: Documentation DocTF labels Dec 5, 2015
@cgundogan cgundogan added this to the Release 2015.12 milestone Dec 5, 2015
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use markdown where you can instead of doxygen tags

@cgundogan
Copy link
Copy Markdown
Member Author

addressed @authmillenon's comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/ udp / UDP and why is RPL the only thing that is not abbreviated here?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am biased (: good hint - will update (most likely later in the morning)

@cgundogan
Copy link
Copy Markdown
Member Author

addressed comments of @OlegHahm

@miri64
Copy link
Copy Markdown
Member

miri64 commented Dec 7, 2015

Since this isn't really an addition, but an enhancement, can you update the PR title and commit message please?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpicky, but I prefer the

Section
=======

Subsection
----------

syntax over the

# Section

## Subsection

syntax. I always think those are comments ^^

@miri64
Copy link
Copy Markdown
Member

miri64 commented Dec 7, 2015

Slightly unrelated but can you @ref net_gnrc "GNRC" GNRC mentions in the mainpage.md, please?

@OlegHahm OlegHahm modified the milestone: Release 2015.12 Dec 7, 2015
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ref net_gnrc "GNRC" otherwise it looks weird in the compiled version

@OlegHahm OlegHahm modified the milestone: Release 2015.12 Dec 7, 2015
@cgundogan cgundogan changed the title gnrc: add documentation gnrc: enhance documentation Dec 7, 2015
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be beneficial to use the @ref <module> "text" syntax here too, to get rid of all the parenthesis

@cgundogan cgundogan added the CI: needs squashing Commits in this PR need to be squashed; If set, CI systems will mark this PR as unmergable label Dec 7, 2015
@cgundogan
Copy link
Copy Markdown
Member Author

@authmillenon should I squash?

@miri64
Copy link
Copy Markdown
Member

miri64 commented Dec 8, 2015

Please consider cgundogan#8 before squashing.

@cgundogan
Copy link
Copy Markdown
Member Author

@authmillenon I merged your commit but it breaks the doc. Do you know how to fix this?

@miri64
Copy link
Copy Markdown
Member

miri64 commented Dec 8, 2015

It seems to be a parsing issue with 1.8.10. Let's hope the 1.8.9.1 on the doc server does not has this issue (since with 1.8.6 it worked fine)

@cgundogan cgundogan force-pushed the pr/gnrc/doc branch 2 times, most recently from 1a9c6fe to f3559c8 Compare December 8, 2015 12:39
@cgundogan
Copy link
Copy Markdown
Member Author

squashed

@cgundogan cgundogan removed the CI: needs squashing Commits in this PR need to be squashed; If set, CI systems will mark this PR as unmergable label Dec 8, 2015
@miri64
Copy link
Copy Markdown
Member

miri64 commented Dec 8, 2015

ACK and go, when travis is happy.

@miri64 miri64 added the CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR label Dec 8, 2015
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whitespace error in 512 and indentation error

@miri64
Copy link
Copy Markdown
Member

miri64 commented Dec 8, 2015

Regarding #4415 (comment): reported it to doxygen https://bugzilla.gnome.org/show_bug.cgi?id=759177

@cgundogan
Copy link
Copy Markdown
Member Author

@authmillenon: addressed your comments and squashed

@miri64
Copy link
Copy Markdown
Member

miri64 commented Dec 9, 2015

Then gogogo. ;-)

miri64 added a commit that referenced this pull request Dec 9, 2015
@miri64 miri64 merged commit 877e070 into RIOT-OS:master Dec 9, 2015
@cgundogan cgundogan deleted the pr/gnrc/doc branch December 9, 2015 11:10
@OlegHahm
Copy link
Copy Markdown
Member

OlegHahm commented Dec 9, 2015

Cool! Thanks for the effort!

@OlegHahm OlegHahm added the Process: needs backport Integration Process: The PR is required to be backported to a release or feature branch label Dec 9, 2015
@OlegHahm
Copy link
Copy Markdown
Member

OlegHahm commented Dec 9, 2015

Hm, maybe it's stupid, but I think this should be added to the release branch, too.

@miri64
Copy link
Copy Markdown
Member

miri64 commented Dec 9, 2015

Doxygen 1.8.9.1 does not have a problem with the fenced code either :)

@OlegHahm OlegHahm mentioned this pull request Dec 14, 2015
24 tasks
@cgundogan cgundogan removed the Process: needs backport Integration Process: The PR is required to be backported to a release or feature branch label Apr 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: doc Area: Documentation Area: network Area: Networking CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants