diff options
authorIan Jackson <>2018-02-09 21:49:49 +0000
committerIan Jackson <>2018-06-16 12:25:49 +0100
commit257ed0b02dadd4538f515807189acdd95d88c320 (patch)
parent880af0a90f1b02db4607e94d38555f2e86af47a3 (diff)
git-debrebase: some notes about gbp import
Signed-off-by: Ian Jackson <>
1 files changed, 28 insertions, 0 deletions
diff --git a/NOTES.git-debrebase b/NOTES.git-debrebase
index c268d75..0d7bea8 100644
--- a/NOTES.git-debrebase
+++ b/NOTES.git-debrebase
@@ -140,3 +140,31 @@ will-overwrite to the current tip (see rules above, which show that
this is OK). Or maybe to the last pseudomerge on the current tip,
so that the overall result will be series of pseudomerges.
+import from gbp
+ inputs:
+ current HEAD (patches-unapplied),
+ this is going to be the base of the old breakwater
+ nominated upstream
+ checks:
+ HEAD:<upstream> = upstream:<upstream>
+ upstream..HEAD:<upstream> is empty (overrideable)
+ upstremm:debian is empty (overrideable)
+ procedure:
+ construct
+ run gbp pq import to generate pq branch
+ new breakwater is
+ old HEAD
+ commit to remove d/patches
+ breakwater pseudomerge with upstream
+ "rebase" of pq branch, each commit with d/patches stripped
+what about dgit view branch ?
+ideally, would make pseudomerge over dgit view
+would need to check that dgit view is actually dgit view of
+ ond of our ancestors
+failing that first push will need --overwrite