diff options
author | agx <agx@web> | 2009-11-07 20:07:39 +0100 |
---|---|---|
committer | Wiki User <wikwik@wiki.sigxcpu.org> | 2009-11-07 20:07:39 +0100 |
commit | 2596f94f732c39f8b8286af4f4dcf9fe677f2b14 (patch) | |
tree | 8044028177c89967cc9f7b6f5f337026accf9c31 /development/debian_packages_in_git.mdwn | |
parent | 9857d8a5a4a773f2d3fcc5e64b24414f1f88a2ec (diff) |
gbp-pull --redo-pq
Diffstat (limited to 'development/debian_packages_in_git.mdwn')
-rw-r--r-- | development/debian_packages_in_git.mdwn | 12 |
1 files changed, 5 insertions, 7 deletions
diff --git a/development/debian_packages_in_git.mdwn b/development/debian_packages_in_git.mdwn index b737b0c..f0a0365 100644 --- a/development/debian_packages_in_git.mdwn +++ b/development/debian_packages_in_git.mdwn @@ -67,15 +67,13 @@ you do: gbp-pull This will update all necessary branches to what other developers might have -pushed in the meantime. If you're also using patch-queues as described above -you additionally have to refresh your *patch-queue* branch: +pushed in the meantime. If you're also using a patch-queue as described above +you can refresh that too in one step: - # Update to what others might have pushed - git-branch -D patch-queue/master - gbp-pq import - git checkout master + # Update to what others might have pushed and rebuild patch-queue + gbp-pull --redo-pq -Future versions of *gbp-pull* will allow you to do all the above steps at once. +This will additionally drop your current patch-queue branch and recreate it from debian/patches. # Preparing a Backport I keep backports on a separate *bpo-<release>* branch like *bpo-lenny*: |