https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101327
--- Comment #4 from anlauf at gcc dot gnu.org --- (In reply to Steve Kargl from comment #3) > I no longer have the ability to commit changes, > so I won't being submitting patches to fortran@ > and gcc-patches@ for review. I'll simply add > patches to bug reports and move on. You rarely say whether the patch regtests fine. Would be a nice-to-have. > My current method of development: > > 1) git clone humble into gccx/ > 2) Develop a patch and test patch. > 3) git diff HEAD > prXXX.diff > 4) Place diff into PR. > 5) Repeat 2)-4) until gccx/ tree gets messed up > 6) rm -rf gccx/ and goto 1) Probably not the most common nor most efficient workflow when using git... Anyway, the current patch is obvious enough. I could commit it for you.
