On Sun, Jun 29, 2025 at 08:36:38PM +0200, Andre Vehreschild wrote: > > I would do git am pr88076_v1_1.patch or patch -p1 <pr88076_v1_1.patch for > each of the patch files. Then they go where they ought to be.
Thanks. I needed -p1 for v1_5 and v1_6. > Pro tip: create a new branch before doing the git am, then you can just > switch back to master when desired. No where near a pro with git and not paid to learn yet-another-RCS. My usage is fairly limited rm -rf gcc/ git clone URL_to_gcc gcc In gcc/ git reset --hard git diff > ../prXXXXX.diff and with 'git diff' if I add a new file, there is 30 or so minutes of google to learning why the new file does not appear in the diff and how to get it. -- Steve
