You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since I use both ILRepack and latest Cecil as assemblies, it would make things much easier if the cecil changes are merged upstream (we manually merge multiple branches and fixes that are not part of trunk already).
I wouldn't mind helping doing so, but first I was interested to know if that seems feasible and if the changes you did make sense as part of Cecil trunk?
The text was updated successfully, but these errors were encountered:
It's very much feasible.
Now whether these changes make sense as part of Cecil trunk is more of a question for @jbevain.
The changes aren't much, basically:
Win32 resource reader/writer (used in ILRepack to support aspnet merge, which uses Win32 resources)
some memory/perf improvements that may only make sense in a repack scenario
since a couple of days a trivial fix on generic params import
Hey guys, I'm very much interested in limiting the number of forks which all have some fixes. I'm currently working with Mono (almost done) and ILSpy (done) to integrate patches upstream.
Since I use both ILRepack and latest Cecil as assemblies, it would make things much easier if the cecil changes are merged upstream (we manually merge multiple branches and fixes that are not part of trunk already).
I wouldn't mind helping doing so, but first I was interested to know if that seems feasible and if the changes you did make sense as part of Cecil trunk?
The text was updated successfully, but these errors were encountered: