Thanks, Rainer! Looking forward for any more feedback.
On Fri, Apr 11, 2014 at 8:08 AM, Rainer Gerhards
wrote:
> On Thu, Apr 10, 2014 at 11:43 PM, Radu Gheorghe
> wrote:
>
> > Hi,
> >
> > Here's a tentative ToC, that we can iterate on (because I'm 100% I'm
> > missing some important stuff):
> >
On Thu, Apr 10, 2014 at 11:43 PM, Radu Gheorghe
wrote:
> Hi,
>
> Here's a tentative ToC, that we can iterate on (because I'm 100% I'm
> missing some important stuff):
>
> TOC page should contain an overview of what rsyslog is and does. For the
> "does" part, I think the important bits are: gather
Hi,
Here's a tentative ToC, that we can iterate on (because I'm 100% I'm
missing some important stuff):
TOC page should contain an overview of what rsyslog is and does. For the
"does" part, I think the important bits are: gather data from various
sources, parse, modify, buffer it and send it to v
On Tue, 8 Apr 2014, Rainer Gerhards wrote:
Hi all,
while I think it is nice to have a toc functionality inside the new doc,
the current structure does not look very appealing to me. Probably a core
problem is that we try to squeeze in the existing content and build to toc
out of it.
Wouldn't i
Hi all,
while I think it is nice to have a toc functionality inside the new doc,
the current structure does not look very appealing to me. Probably a core
problem is that we try to squeeze in the existing content and build to toc
out of it.
Wouldn't it make sense to sit back a bit and think about
5 matches
Mail list logo
