-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
archaelogy: tracking code damage from automatic (or centralized manual) forward ports in 71X #41396
Comments
A new Issue was created by @slava77 Slava Krutelyov. @Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign reconstruction |
New categories assigned: reconstruction @mandrenguyen,@clacaputo you have been requested to review this Pull request/Issue and eventually sign? Thanks |
I have no recollection (although what you describe rings some bell, but I don't remember what exactly). |
I see this was done as part of #3013 (which technically is visible in the 7_1_0_pre6 release notes, but very easy to miss). |
Indeed, I eventually found it as well. |
No recollection what so ever (i mean was 9 years ago!) |
we were trying to track down a part of the history of changes in RecoTracker/CkfPattern/python/CkfTrackCandidates_cfi.py
specifically, a change in #2291 was merged on Fri Feb 21, 2014 and entered https://github.com/cms-sw/cmssw/releases/tag/CMSSW_7_1_0_pre3
This entered the history as commit ab1d806
After that, based on git log, there is another commit that merges a 70X PR #2410 in commit b0669c7 from Mon Mar 24, 2014. This happened shortly after CMSSW_7_1_0_pre5 was made and does not show up in the following pre-release https://github.com/cms-sw/cmssw/releases/tag/CMSSW_7_1_0_pre6
If I'm not mistaken, the full range of differences is in 17b09fe...da8c157
[later found that] the merge was done as a part of manual centralized forward ports in #3013
@mmusich @mtosi @VinInn @cerati @rovere @makortel
do you recall if this was discussed at some point in the past? I'm trying to understand if there was a partial recovery or if this was forgotten.
@mmasciov
The text was updated successfully, but these errors were encountered: