How do I gather up new code to be converted as patches?

[Jeffrey Hugo]

Generating a patch is "git format-patch".  This command operates on
commits in your local tree.  So you need to commit your changes to
your local tree.  The command for that is "git commit", and it works
on staged changes.  To stage changes, you need to "git add" them.
"git status" can help you visualize unstaged and staged changes.

So, if I had a change in foo.txt, I would likely use "git status" to
view that unstaged change.  Then I can stage it using "git add
foo.txt".  "git status" will then show that it is staged.  Finally, I
will do "git commit", which will ask for a commit text, and commit the
change to the tree.  I can then verify that the change is committed
using "git log".

Does that help you out, or did I misunderstand your situation?

-Jeff

On Wed, Jun 22, 2022 at 11:19 AM Kevin Brace <kevinbrace at gmx.com> wrote:
>
> Hi,
>
> I spent about 2 days trying to figure this out, but I guess not a lot of people do this, so I was not able to find a good example somewhere on the Internet.
> How to I use git to gather up new code to be converted to patches?
> Specifically, I have 20+ new files in one location (drivers/gpu/drm/via) and a small change to DRM main make file (drivers/gpu/drm/Makefile).
> If someone can tell me how to do this, I will post the work on dri-devel.
>
> Regards,
>
> Kevin Brace
> Brace Computer Laboratory blog
> https://bracecomputerlab.com