Merge ~apw/+git/kteam-tools:cranky/checkout--add-roles-for-prepare-and-apply into ~canonical-kernel/+git/kteam-tools:master
Status: | Work in progress |
---|---|
Proposed branch: | ~apw/+git/kteam-tools:cranky/checkout--add-roles-for-prepare-and-apply |
Merge into: | ~canonical-kernel/+git/kteam-tools:master |
Diff against target: |
250 lines (+104/-31) 4 files modified
cranky/cmds.d/checkout (+21/-5) cranky/crl/git.py (+11/-11) cranky/crl/handle.py (+26/-4) cranky/docs/cranking-the-kernel.md (+46/-11) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Canonical Kernel Team | Pending | ||
Canonical Kernel Team | Pending | ||
Review via email: mp+400701@code.launchpad.net |
Commit message
This patch stack adds support to `cranky checkout` for separation of
roles for kernel preparation and patch application. This adds new
command line options to checkout: --prepare-kernels and --apply-patches.
Defaulting to --prepare-kernels for compatibility with current
semantics.
This patch set changes the local branch namespace for cranky generated
branches to `cranky-
to disambiguate clearly which function the local branch fills. It also
simplifies branch destination selection for push.
This patch set changes a number of things:
1) it adds the concept of local_branch to our Handle objects allowing us
to reuse the existing overlap handling used for remotes,
2) it adds the concept of local_branch to our GitHandle object allowing
us to feed roll and source information into the branch selection,
3) adds some extra summary information indicating where the branch
came from (and should push to), and
4) automatically keeps the git concept of upstream branch updated.
This last feature in concert with a simple addition to the users basic
git config allows us to simply `git push` on any `cranky-*/*` branch and
have it go back to whence it came. It is hoped this will simplify or
eliminate the need for a `cranky push`.