Archives
Archives
| From: | Chris White <chris.chriswhite@×××××.com> |
|---|---|
| To: | gentoo-portage-dev@l.g.o |
| Subject: | [gentoo-portage-dev] Porage API Documentation Proposal |
| Date: | Sun, 16 Jul 2006 18:13:52 |
| Message-Id: | 25fffe5a0607161112x1ca6a7a8he7f4f3f0b15bf3c2@mail.gmail.com |
| 1 | Hi all, |
| 2 | |
| 3 | I had a discussion yesterday with the folks and #gentoo-portage regarding |
| 4 | API documentation using epydoc and inline custom doc strings. Attached is a |
| 5 | proposal of what I believe encompasses a majority of the discussion. |
| 6 | Suggestions, comments, etc. are welcome. My standard gentoo account was |
| 7 | doing weird things with mailing list subscriptions, so I'll be using my |
| 8 | gmail account instead. |
| 9 | |
| 10 | Chris White |
| File name | MIME type |
|---|---|
| portage_documentation_proposal.txt | text/plain |
| Subject | Author |
|---|---|
| Re: [gentoo-portage-dev] Porage API Documentation Proposal | Zac Medico <zmedico@g.o> |
| Re: [gentoo-portage-dev] Porage API Documentation Proposal | Brian Harring <ferringb@×××××.com> |
| [gentoo-portage-dev] Re: Porage API Documentation Proposal | Chris White <chris.chriswhite@×××××.com> |