
Devs, Austin
I've found out what the problem was, and fixed it.
What is the right way to re-do all this? My thought:
* git revert 3cf8ecd
I think this will re-apply all my patches, in one go.
(call this new path 'foogle')
* apply the fix as a new patch
* validate
The history will look odd. In particular, if someone does 'git blame' then lots of unrelated changes will all map to 'foogle'. And 'foogle's commit message will say "revert a revert of 10 patches". Which is not helpful.
Best would be to re-apply the patches one by one I suppose. How could I do that?
Simon
| -----Original Message-----
| From: ghc-tickets [mailto:ghc-tickets-bounces@haskell.org] On Behalf
| Of GHC
| Sent: 14 May 2015 22:26
| Cc: ghc-tickets@haskell.org
| Subject: Re: [GHC] #10359: Tuple constraint synonym led to asymptotic
| performance lossage
|
| #10359: Tuple constraint synonym led to asymptotic performance lossage
| -------------------------------------+--------------------------------
| --
| -------------------------------------+---
| Reporter: axch | Owner:
| Type: bug | Status:
| closed
| Priority: normal | Milestone:
| Component: Compiler | Version: 7.6.3
| Resolution: fixed | Keywords:
| Operating System: Linux | Architecture:
| x86_64
| Type of failure: Runtime | (amd64)
| performance bug | Test Case:
| Blocked By: | perf/should_run/T10359
| Related Tickets: | Blocking:
| | Differential Revisions:
| -------------------------------------+--------------------------------
| --
| -------------------------------------+---
|
| Comment (by Austin Seipp