[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2edcbc94-e29a-b8ab-e320-ee52788471c8@gmail.com>
Date: Mon, 24 Oct 2022 16:16:25 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Li kunyu <kunyu@...china.com>
Cc: krisman@...labora.com, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] unicode: mkutf8data: Add compound malloc function
On 10/24/22 15:26, Li kunyu wrote:
>
> I send the 1/2 and 2/2 patches separately, and divide the two functions and related modifications in the 2/2 patch into two patches.
>
No, not that way.
Here's the recipe for submitting patch series (a set of two or more patches),
assuming that you do the work on a branch which is based on mainline (master):
1. First, create directory which to store the patches.
2. Determine the base commit for your branch. Most of the times `git merge-base
master <your branch>` can be used, but sometimes you need to determine that
manually by seeing the commit log with `git log`.
3. Generate the patch series (preferably with cover letter) by `git format-patch
-o <directory> --cover-letter --base=<base commit> <base commit>`. You can
now write the description about the series in the cover letter (which will
be 0000-cover-letter.patch).
4. Find the maintainers which will review your series with
`scripts/get_maintainer.pl /path/to/directory/*.patch`. Ignore your email
address if it exists.
5. Send the series with `git send-email <--to and/or --cc maintainers>
/path/to/directory/*.patch`. All patches will be sent as reply to the
cover letter.
Thanks.
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists