Processed: Re: Bug#474590: [frontend] add a parsable reason for overrides and optionally require it

Processing commands for cont...@bugs.debian.org: tags 474590 + patch Bug #474590 [lintian] [frontend] add a parsable reason for overrides and optionally require it Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 474590:

Bug#474590: [frontend] add a parsable reason for overrides and optionally require it

tags 474590 + patch thanks Hi I am considering to the attached patch to the master branch. It solves collecting the override comments and printing them (with --show-overrides). A comment is not carried through to the next override (of same tag); but this is matter of updated file_overrides.

Bug#474590: [frontend] add a parsable reason for overrides and optionally require it

block 512901 with 474590 thanks Hi all, After thinking for a while about how to implement 474590 I think an approach like the one propposed in 512901 would be the best. This is based on two points: * First, comment lines are already supported: adding something on the same line as the tag

Bug#474590: [frontend] add a parsable reason for overrides and optionally require it

Raphael Geissert atom...@gmail.com writes: The implementation of #512901 is still a bit tricky because the comments need to be made available next to the overridden tags when --show-overrides is used so that reporting/harness sees them. Russ or anyone else: is there any suggestion on what