please sponsor arp-scan

[Gianfranco Costamagna]

>I'm never sure of the amount of details to put into the changelog file.
>Is there some kind of guideline?


none I'm aware of :)
>* I intentionally did not put a changelog entry for the removed patch
>  file; I think what you wrote ("Drop old bsd patch") is misleading:
>  If I read that I think that the code now different because a patch
>  was dropped.  The patch was really dropped when it was removed from
>  the series file…


I wrote "old" just because it was "useless now", so, it doesn't matter
too much if it has been dropped from series or just the file, the 

patch is useless anyway
but you are right, it should have been more explicit

>* As for the lintian override, that was a one-time needed fix for the
>  imported kali version; since the changelog for the version introducing
>  the override did not mention it, i thought mentioning its removal is
>  more confusing than useful.


I think such changes are worth mentioning, because they indicate that the package
is more "Lintian clean" now, but you might be right that we should ship
changelogs mentioning stuff that our users care, not internal changes.

I usually create changelog with "gbp dch", so each git is a newline there.
Verbosity is cheap, but we shouldn't add too much stuff.

To answer, I don't know which is better, but with a changelog of 3 lines, adding one or
two more doesn't hurt too much :)
(e.g. updating an email address might be worth mentioning, so people know that before
reporting a bug they should update their address book)


G.