Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 636980 - Consider dropping commit complete output, RepoMan sez:....
Summary: Consider dropping commit complete output, RepoMan sez:....
Status: RESOLVED WONTFIX
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Repoman (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-09 16:30 UTC by William L. Thomson Jr.
Modified: 2022-07-12 03:18 UTC (History)
3 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 William L. Thomson Jr. 2017-11-09 16:30:07 UTC
A request for consideration. I can easily address this myself for my own needs. Though it may apply to others thus bug for consideration. There likely was a time when repoman output on commit was beneficial. When doing lots of commits, it just becomes more noise. Not to mention a bit redundant. Upon a successful commit, you already get output from git.

* 1 files being committed...
...
 1 file changed, 1 insertion(+), 1 deletion(-)

Not sure there is any benefit to having additional

Commit complete.
RepoMan sez: "If everyone were like you, I'd be out of business!"

Seems cute or something the first time. But after you see it thousands of times, it loses its appeal. I can make a patch to drop/remove locally. But maybe others feel the same way. Maybe its time for this to go and be a thing of the past. I think the git output is suffice, and nothing need be said by repoman. Only when there is issue.

Thank you for considering this request.
Comment 1 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-07-12 03:18:24 UTC
repoman support has been removed per bug 835013.

Please file a new bug (or, I suppose, reopen this one) if you feel this check is still applicable to pkgcheck and doesn't already exist.