Some people use {X,}-MFC: {NO,no,never} to mark commits to not be
MFCed. Searching your ocmmits manually and putting them in an
exclude file is tedious so automate this.
Details
- Reviewers
emaste
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 53830 Build 50721: arc lint + arc unit
Event Timeline
Probably not the most elegant solution and adds awk as a dependency but seems to work.
Other ones I was pondering which is used more often is "X-MFC with" to sort them together (a bit more tricky to implement) and X-MFC to: (to sort out commits_to which are not intended to be MFCed to the target branch). Probably should be options...?
Basically I didn't want to lose this and put it out for further consideration.
Any reason we do also add an exclude file? You never really know at commit time for some changes. Later you discover the problems...
Apart from this adding yet another pass over all the commits since the branch point, it isn't bad.
I have a similar script I should see if it's better or not...
We support an exclude file already, with -X exclude_file.
I don't object to this functionality but am worried about increased runtime. We could perhaps check only the candidates found, i.e. in the while read hash; do loop just below?
Love -X... somehow missed it.
Maybe we should add per stable branch versions of it? My FreeBSD changes are a big false positive hit for example
I think I should have abandoned it. Not that I love Lua but -X has since done my job, especially since -X can have comments.