https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
Mikael Morin <mikael at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikael at gcc dot gnu.org
--- Comment #5 from Mikael Morin <mikael at gcc dot gnu.org> ---
(In reply to kargl from comment #0)
>
> 4) I don't use git. I tried to do 'git add libgfortran/intrinsics/trigpi\*'
> followed by 'git commit libgfortran/intrinsics/trigpi\*', and then
> finally 'git diff > z_halfcycle.diff'. This does not generate one
> unified diff file. Sigh. I'll attach the new files along with the
> mangled diff.
With git you need to add all the files, not only the new ones (you can use git
add --update to add the existing files).
Then the patch can be generated (if you don't commit) with git diff --staged
If you commit, you need to add an argument to git diff to tell him a reference
to compare against, namely origin/master (remote master), master (local
master), HEAD^ (last commit before the tip of the branch), etc. The default
reference if omitted is the tip of the branch, what you have just committed, so
the diff is empty.
