π Developer Guides#
Git Repositories#
erofs-utils#
erofs-utils is developed with Git, and multiple branches are available for different needs:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git
branch |
description |
rebase? |
---|---|---|
dev |
erofs-utils development tree |
Maybe |
experimental |
erofs-utils tree with unstable patches for testing |
Yes |
master |
erofs-utils stable tree |
No |
Linux kernel source#
If youβre interested in EROFS kernel development, itβd be much better to keep your local code in sync with the latest EROFS development repo:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git
branch |
description |
rebase? |
---|---|---|
fixes |
EROFS kernel fixes-only tree (for this cycle) |
Yes |
dev |
EROFS kernel development tree (for the next cycle) |
Yes |
Mailing List#
EROFS has its own development mailing list hosted by OzLabs: <linux-erofs@lists.ozlabs.org>
You can subscribe to the mailing list to receive the latest status of EROFS.
When posting, itβd be much helpful to:
Add an additional tag in the subject like
[PATCH]
,[question]
or[bug report]
, etc.;Avoid top-posting if possible.
All patches should follow the Linux kernelβs coding style. Additionally, as one of Linux kernel development communities, patches require the βsign-offβ procedure.
The sign-off should be appended as a simple line at the end of the commit message for the patch, which claims that you agree to Developer Certificate of Origin. In other words, it certifies that either you wrote it or have the right to pass it on as an open-source patch.
Then you just add a line saying:
Signed-off-by: Random J Developer <random@developer.example.org>
using your real name (sorry, no pseudonyms or anonymous contributions.)