When you scratch built the package and you got a successful mail from the build system you are ready to commit your changes.

From the branch where you made your changes, just do a:

git commit -vsa

And on Top of your commit message write what has changed.

For example:

[PATCH v2 n/m] grep: Update to Version x.y

If this commit has more patches, then n/m must be used.

We recommend the following Tags:

  • This is an Update release
  • This is a Bug-fix release
  • This is a Security-fix release (with changes what was fixed)

Then add a useful Bug description, if this is a BUG:

Fixes: #11064

And a short description

Push your changes to your upstream repository

Now you can push your changes to your server-branch with:

git push <username> <branch-name>

Send patch to patchwork

And finally send your commit to the patchwork server:

git send-email -1

Send second patch (if needed)

Was a recent patch recently sent and there is an error? A second patch -v2 can easily be sent to update the package.

git send-email -1 -v2 -in-reply-to <msg-id of email from last patch>

Note: Version 2 is -v2. Version 3 becomes -v3, etc.

To obtain the msg-ID from eMail

1) Locate the original email with the patch error.

  • For Apple Mail - Drag and drop that first patch email message from Apple Mail to the Desktop
  • For gmail - Download message to the Desktop
  • Both of these apps download an .eml file.

2) Open the email with a text editor and search for Message-Id:

3) or enter this command: grep Message-Id: <fileName>

# example
$ grep Message-Id: exampleEmail.eml 
Message-Id: <20220426563412.1234567-1-example@domain.org>
# then do:
git send-email -1 -v2 -in-reply-to 20220426563412.1234567-1-example@domain.org

The -in-reply-to switch is used to make the email look like a single thread in the email program. All email, regarding one commit, are in one place and easily to see.

Now your patch is awaiting approval!