Overview data on rebuilding

[Russ Allbery]

Julien ÉLIE <julien at trigofacile.com> writes:

> Already done yesterday (it was my revision 8021).
> makehistory was not regenerating :lines by the way (always empty)
> and :bytes was only art->len computed by storage methods so I had
> to reparse the article in order to remove dot-stuffing and "-3" for
> the final .CRLF, as well as counting lines.
> That was why I thought it was going to be slower because we previously
> did not have to parse the article.
>
> I also fixed :bytes last week when innd generates it.

Oh, excellent.

> I do not know why it was done.  I hope it does not break something if we
> leave them.  I know that OVER will not use it but "HDR Bytes" yes
> (contrary to "HDR :bytes").

It shouldn't break anything.  The standard specifically warns about that
behavior, too.

>>        other headers.  It SHOULD NOT alter, delete, or reorder any
>>        existing header field except the Path header field.

> Only Path:?  What for Xref:?

Serving agents and relaying agents are allowed to modify Xref.  Injecting
agents aren't, but since injecting agents immediately hand the article to
a relaying agent, it doesn't actually matter.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.