Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 565538 - egencache --update-changelog: please allow exclude of lines in changelog messages
Summary: egencache --update-changelog: please allow exclude of lines in changelog mess...
Status: CONFIRMED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-11 20:50 UTC by Robin Johnson
Modified: 2015-11-13 07:42 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2015-11-11 20:50:55 UTC
ChangeLog messages presently include a lot of trailing metadata, such as this:
  Package-Manager: portage-2.2.23
  Package-Manager: portage-2.2.20-prefix
  Signed-off-by: Lars Wendler <polynomial-c@gentoo.org>
  RepoMan-Options: --ignore-arches
  Gentoo-Bug: 564662

Collectively, this accounts for at least 653KiB in the current tree (based on count of commit messages, which would be higher if a single commit impacts multiple ChangeLogs).

Should we consider excluding some or all of these from ChangeLog messages? They would still be available in the git commit messages.

If we exclude only '^Package-Manager: ...', we will save at least 387KiB in the ChangeLogs.

Please add an option:
--changelog-ignore-logline-trailing-footer-regex '^Package-Manager: portage-[.0-9_]+$'
That omits any trailing footer commit log lines matching the regex from the ChangeLog.

For completeness and testing, you might also want to add:
--changelog-ignore-logline-regex '...'
which applies to all lines of a commit log.
Comment 1 Andrew Savchenko gentoo-dev 2015-11-12 13:28:19 UTC
"Gentoo-Bug:" entries should stay in the log, as they provide valuable link for users (e.g. they can read more details about bug).