you add a new license, but also modify profiles/license_groups). If the change affects multiple directories, but is mostly related to a particular subsystem, then prepend the subsystem which best reflects the intention (e.g.
Commits that affect primarily a particular subsystem should prepend the following code to the first line of the commit message:.Optional detailed multiline explanation must start at the third line.If CATEGORY/PN is very long and the 75 character limit is impossible to obey, it is OK to exceed the limit in this case.One may break atomicity in order to make a commit pkgcheck-valid (or you should reconsider the order you commit in, e.g.Split version bumps and ebuild cleanup in separate commits (makes reverting ebuild removals much easier).Commits in git are cheap and local, so use them often.pkgcheck scan must be run from all related ebuild directories (or related category directories or top-level directory) on the tip of the local master branch (as in: right before you push and also after resolving push-conflicts).Every commit on the left-most line of the history (that is, all the commits following the first parent of each commit) must be GPG signed by a Gentoo developer.Commits may span across multiple ebuilds/directories if it's one logical change.All commits must be pkgcheck-valid (exceptions only on right-hand branches).7.9 Automatic git pull/rebase merge involving conflicts with KEYWORDS.7.8 A cli-tool to crawl through pull requests.7.7 Retaining commit author information.7.6 Preventing 'git repack -a' from touching huge packs.7.5 Grafting Gentoo history onto the active repository.7.3 Using the gentoo git checkout as your local tree.6.2 Pull requests from developers and users.