For example, you might be modifying d-i for a derivative distribution, so a branch containing your distro-specific changes would make sense. If you're needing to update or maintain your changes in the medium or long term, consider publishing them in a branch.Anyone can do this, you don't need to be a member of the DebianInstaller team. You can generate the patches with "git format-patch".
If in doubt, publish your patches to the mailing list, or to a bug report, for review. ( Checkout instructions here.) These rules are intentionally loose, the intent is to evolve best practices and procedures organically and document them here. Some guidelines for using the DebianInstaller git repositories. While you can check out just a single git repository if you will only be working on a single component of DebianInstaller, most of us use the mr tool to mass checkout and update the many repositories that constitute d-i. If you're new to git, a good explanation of using it in this centralized way, that should be easy to pick up if you've used Subversion, was published here: The only difference from this tutorial is that we use "people//foo" for publishing personal branches, while the tutorial uses "/foo". (Not to be confused with Ubuntu's version!) The repositories contain the canonical version of DebianInstaller. Everyone on the DebianInstaller/Team can commit to any of the repositories. The DebianInstaller git repositories (one per source package) are used in a generally centralized way. A web view the git repositories may be found here:
0 kommentar(er)
