Welcome to the website of subpatch. The tool that does multi repository management right. Don't worry, stay relaxed!
If you are currently using git-submodules or repo and you are frustrated, subpatch will be mostly your solution! If you are interested, email me.
Note: subpatch is not production ready. It's currently a prototype. Nevertheless please try it out and give feedback. I will incorperate it.
If you want to try out the subpatch tool really quickly, follow the instructions:
# First go into the toplevel directory of your project that is using git, ...
$ git status
# then download the subpatch python script, ...
$ wget https://subpatch.net/downloads/latest/subpatch
$ chmod +x ./subpatch
# and finally add a subproject to your (super)project!
$ ./subpatch add https://github.com/google/googletest external/googletest -r v1.15.2
$ ./subpatch status
$ git commit -m "adding googletest"
$ ./subpatch status
If you are interested in finding out more, please see the text below and the website. It contains explanations, tutorials, how-to guides and references about subpatch.
subpatch is interesting for you if you want to do the following tasks:
- assemble a monorepo from multiple repositories
- integrate third party dependencies into your project as source files
- maintain a local fork (with a linear patchstack) of an upstream project
subpatch is a multi-repository management tool based on the following ideas:
- It's based on
git add. The files of subprojects are added as normal files to the superproject. - Subprojects are in most cases just other git repositories.
- The metadata of a subproject is saved in a git-config styled configuration file.
- Modifications of the subproject are possible and subpatch helps to maintain a linear patch stack of the modifications.
- Importing new versions of the subproject is possible and subpatch helps to rebase the local modifications.
When you use subpatch the subprojects are not git repository itself. The files of the subprojects are added as files to the superproject. You will only have to deal with a single git repository.
This is in contrast to other tools, e.g.
These tools manage multiple git repositories at once. Based on a manifest file multiple git repositories are cloned from different upstream sources into your local checkout.
The page Comparison to other tools describes the differences in more detail.
On the subpatch website you find more information and the documentation, e.g. explanations, tutorials, how-to guides and references. New software releases are announced on the release notes page, including the release notes and changelog.
For support, dicussions and feature requests you can
- join the matrix room #subpatch:matrix.org,
- open an issue on github or
- email me.
The source code of the program and the website can be found in the git repository github.com/lengfeld/subpatch.
I have licensed the source code of subpatch as GPL-2.0-only, It's the same license that is also used for the Linux kernel or git itself.
I licensed the content of the website as Creative Commons Attribution-ShareAlike 4.0 International / CC BY-SA 4.0. In short this means: you can use the work, must give attribution, can use it commercially, too, and you must release derived work under the same license.
When you contribute, please add your sign-off. See Developer's Certificate of Origin for details. It's used in the Linux kernel and other projects.
Note: For now the project does not welcome code contributions yet. The code is in a very rough state (in average one TODO comment per 10 lines of code). So don't waste our time trying to implement features. I want to get the internal architecture right first. Nevertheless, feedback and comments to the tool and concepts is very welcome.
The standard license header and warranty disclaimer of the GPLv2 is:
Copyright (C) 2024 Stefan Lengfeld
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; as version 2 of the License.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
