#include <hallo.h> * Jari Aalto [Sat, Feb 04 2006, 04:36:55PM]: > Eduard Bloch <[EMAIL PROTECTED]> writes: > > > #include <hallo.h> > > * Jari Aalto [Sat, Feb 04 2006, 01:16:06PM]: > > > >> Package: svn-buildpackage > >> Version: 0.6.14 > >> Severity: wishlist > >> > >> The manual pages in current form are very clinical and suppose high > >> technical level of understanding how the development process goes. It > >> would be good if in each manual page, there were section > > > > Have you visited /usr/share/doc/svn-buildpackage already? Is that > > sufficient or do you want more? > > Yes I have. I wasn't clear enough in the message. I wold like to > see some kind of "crash course" or "reminder" in the EXAMPLES section > of the man pages, so that the "standard work flow" could be seen > in one glance.
Reality check please! Do you expect the g++ manpage to be a C syntax reference and describe every bit of OOP, plus make tutorial and autotools guide to explain the standard workflow? > I Mean: > > 1. Hack Debian > 2. BE away in other projects > 3. .. back to debian after months > 4. ?? Eh, I've forgotten the routine > 5. ?? Hm, the command was XXX, let's read man page, maybe it > brings to my mind... > 6. Erm, no EXAMPLES section here ... SEP. If you forgot the knowledge, go the same way as the first time to get it. I am not there to teach everyone doing everything and looking in new-maint-guide or dev-reference from time to time is not a reason to be ashamed. > The /usr/share/doc/svn-buildpackage could be the full manual > and EXAMPLES would give typical examples how commands are applied. If you wish to see a noob-style guide, write one and I most likely would add it to the package. Eduard. -- <Getty> totenstille? <Getty> mal nen ping auf mich selber machen... <Getty> ist ja grausam <Getty> 2 minuten lang in keinem channel nen wort <Alfie> Getty: Mach ein /unignore * <Getty> schaemt ihr euch nicht? <Getty> nichtmal alfie sagt was <Getty> unglaublich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
