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

[Kevin Brace]

Hi Jeffrey,

I did not point to the repository I actively maintain, but since I was able to do so since 2017, I think I have figured out all of what I consider "basic" ways of using git to maintain and keep up with the upstream DRM code.

https://cgit.freedesktop.org/openchrome/drm-openchrome/

It is just that I am now at a point of posting code on dri-devel mailing list for the first code review, but I just suddenly realized that git does not appear to have a convenient way to do this.
What I am trying to do is to post the code on dri-devel like the previous OpenChrome developer, James Simmons, did in 2013.

https://lists.freedesktop.org/archives/dri-devel/2013-June/039594.html

Regards,

Kevin Brace
Brace Computer Laboratory blog
https://bracecomputerlab.com


> Sent: Wednesday, June 22, 2022 at 12:33 PM
> From: "Jeffrey Hugo" <jeffrey.l.hugo at gmail.com>
> To: "Kevin Brace" <kevinbrace at gmx.com>
> Cc: "open list:DRM PANEL DRIVERS" <dri-devel at lists.freedesktop.org>
> Subject: Re: How do I gather up new code to be converted as patches?
>
> 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
>