!4 update en/Community-Developer-Guides/Source_Package_Git_Workflows.md.

Merge pull request !4 from wucaiheng/N/A
This commit is contained in:
delong 2023-03-27 09:45:13 +00:00 committed by Gitee
commit 13b903d572
No known key found for this signature in database
GPG Key ID: 173E9B9CA92EEF8F
1 changed files with 2 additions and 2 deletions

View File

@ -254,7 +254,7 @@ git commit
git push
```
Then it's a matter of operating on the hosting platform and committing a PR from your own repository to the upstream community.
Then it's a matter of operating on the hosting platform and committing a PR from your repository to the upstream community.
If there are updates upstream, you have to sync the upstream changes before committing the PR, resolve the conflicts, and then commit the PR
@ -309,7 +309,7 @@ git push --tags
If the native branch involves binary changes, the generated patch will also have binary information, and the buildpackage will prompt ``detected 1 unwanted binary file (add it in debian/source/include-binaries to allow its inclusion)`
debian recommends putting the binaries you want to replace in the debian directory, then modifying the install step in debian/*.install or debian/rules to overwrite the upstream binaries at build time. debian includes binaries, whether they are images or patches, that need to be added to debian/source/include-binaries, or just add a line to debian/source/options to include-binaries, allowing any binary to be included.
Debian recommends putting the binaries you want to replace in the debian directory, then modifying the install step in debian/*.install or debian/rules to overwrite the upstream binaries at build time. Debian includes binaries, whether they are images or patches, that need to be added to debian/source/include-binaries, or just add a line to debian/source/options to include-binaries, allowing any binary to be included.
https://www.debian.org/doc/manuals/debmake-doc/ch08.en.html