[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#824908: apt: inconsistent “header” terminology throughout documentation, comments, messages



Howdy David,

Thank you for caring about the documentation and source, I am very
glad of the review of my proposed changes.

On 24-May-2016, David Kalnischkies wrote:
> RFC2440 refers to a "key-value pair" as "Armor Header" (in that
> casing). A collection of those is called "Armor Headers" – compare
> §6.2 (especially the two paragraphs above the "Armor Header Key"
> list).

Thank you. I have removed those changes and left that standard
terminology in place.

> > rfc822-style
> 
> If I have seen it right, we talk about our own method-interface
> here, which for self-containment is probably better described as
> deb822 style as we have that around as a manpage while rfc822 deals
> with all sorts of things not applying to us.

The deb822-style describes formats like the package control fields.

I confusingly wrote “RFC 822” when referring to APT's HTTP-style
protocols. It just doesn't apply.

> > rfc2616
> 
> Is superseded by now (7230-7237), so it shouldn't be referred to anymore
> the HTTP protocol anymore.

I have updated the commit messages to reflect the current HTTP
standards for those cases.

Please let me know whether you require further changes in
<URL:https://notabug.org/bignose/debian_apt/commits/wip/issue/824908/terminology-header-fields>
to accept the merge.

-- 
 \     “I have an answering machine in my car. It says, ‘I'm home now. |
  `\  But leave a message and I'll call when I'm out.’” —Steven Wright |
_o__)                                                                  |
Ben Finney <ben@benfinney.id.au>

Attachment: signature.asc
Description: PGP signature


Reply to: