- Change Subsections of Chapter 5 into Sections to preserve
right gerarchy git-svn-id: svn://svn.gna.org/svn/sgpemv2/trunk@221 3ecf2c5c-341e-0410-92b4-d18e462d057c
This commit is contained in:
parent
a71982d4dc
commit
a63937f0e4
|
@ -585,7 +585,7 @@ to automatically associate the @samp{.tcc} extension to
|
|||
the @samp{c++-mode}.
|
||||
|
||||
@item
|
||||
Constructor initialization list use the following format:
|
||||
Constructor initialization list uses the following format:
|
||||
@verbatim
|
||||
C::C(T1 arg1, T2 arg2, ...) :
|
||||
m1(arg1), m2(arg2)...
|
||||
|
@ -1074,7 +1074,7 @@ practice, locking seems to inhibit productivity more than anything else.
|
|||
@chapter Using the Mailing List
|
||||
@cindex mailing list
|
||||
|
||||
@subsection Introduction and goals
|
||||
@section Introduction and goals
|
||||
|
||||
This mailing list (often referred from now on simply as ``ML'') has been
|
||||
created with the specific aim of coordinating the effort of the members
|
||||
|
@ -1088,7 +1088,7 @@ This very chapter (an approved draft) you're reading can be amended
|
|||
too. For more informations, please refer to the corresponding
|
||||
subsection, called ``A democratic discussion''.
|
||||
|
||||
@subsection About the language, some useful conventions
|
||||
@section About the language, some useful conventions
|
||||
|
||||
The English language (either the UK or the US one, but the slangwords)
|
||||
is believed to be the best choice to deliver our internal
|
||||
|
@ -1128,7 +1128,7 @@ form. You can find a nice article on this by searching @emph{Wikipedia}.
|
|||
This doesn't forbid you to use Italian for normal communications over
|
||||
the ML.
|
||||
|
||||
@subsection Steer the wheel
|
||||
@section Steer the wheel
|
||||
|
||||
Most discussions start with a draft, like this. The talking then goes on
|
||||
amendating the document and, when no-one opposes it anymore, the draft is
|
||||
|
@ -1144,7 +1144,7 @@ this procedure, although unlikely (usually, it's an internal task).
|
|||
|
||||
This draft is hence subject to change in this aspect.
|
||||
|
||||
@subsection A democratic discussion
|
||||
@section A democratic discussion
|
||||
|
||||
Of course, not everybody has to agree with everyone else on every
|
||||
subject. We're just humans, after all; we're entitled to our opinion.
|
||||
|
@ -1162,7 +1162,7 @@ if no further points to discuss are raised in such time, the document
|
|||
is marked as agreed. The minimum number of days for a votation / to amend
|
||||
a draft is set to three.
|
||||
|
||||
@subsection Keeping the archives clean
|
||||
@section Keeping the archives clean
|
||||
|
||||
If, by writing your response, you've to comment on things that pertain to
|
||||
@emph{different} @acronym{KA}s, or if the discussion requires to
|
||||
|
@ -1174,7 +1174,7 @@ Not only this makes easier to search throughout the archives; it makes
|
|||
easier for others to reply only to those matters that concern they,
|
||||
tidily continuing the tree structure of threads.
|
||||
|
||||
@subsection Diving in technicalities
|
||||
@section Diving in technicalities
|
||||
|
||||
E-mails should be sent out text-only, not in @acronym{HTML} format.
|
||||
This makes them faster to download, store, manipulate, and it even
|
||||
|
@ -1238,8 +1238,8 @@ Finally approved on date: <YYYY, Month DD>
|
|||
----------------------------------------
|
||||
@end example
|
||||
|
||||
Of course, the @samp{``rejected by''} list should ideally be empty, or just
|
||||
listing @samp{``nobody''}. The subject area is up to the writer to purpose,
|
||||
Of course, the @samp{rejected by} list should ideally be empty, or just
|
||||
listing @samp{nobody}. The subject area is up to the writer to purpose,
|
||||
wisely. Different areas are instantiated as need arises. Please don't
|
||||
create a forest of areas; it's no use whatsoever.
|
||||
|
||||
|
|
Loading…
Reference in New Issue