From 58cd6d7cf9c2e0c5faba010744079881da008fea Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Sun, 25 Mar 2018 12:33:28 +0100 Subject: git-debrebase: maintain debrebase-last This is mostly for the benefit of dgit(1), which wants to know whether to run gdr to do quilt fixup. Signed-off-by: Ian Jackson --- git-debrebase.5.pod | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) (limited to 'git-debrebase.5.pod') diff --git a/git-debrebase.5.pod b/git-debrebase.5.pod index fb9cff2..dce648e 100644 --- a/git-debrebase.5.pod +++ b/git-debrebase.5.pod @@ -257,6 +257,12 @@ the interchange and breakwater branches may be identical, in which case the unstitched branch is fast forward from the interchange branch and no pseudomerge is needed. +When ffq-prev is not present, +C records some ancestor of refs/B, +(usually, the result of last stitch). +This can be used to quickly determine whether refs/B +is being maintained in git-debrebase form. + =head1 OTHER MERGES Note that the representation described here does not permit @@ -304,7 +310,8 @@ or both. =item Launder branch Record the previous tip in ffq-prev, -if we were stitched before. +if we were stitched before +(and delete debrebase-last). Reorganise the current branch so that the packaging changes come first, @@ -340,7 +347,8 @@ Make a pseudomerge, whose contributing parent to is the unstitched branch and whose overwritten parent is ffq-prev, -consuming ffq-prev in the process. +consuming ffq-prev in the process +(and writing debrebase-last instead). Ideally the contributing parent would be a laundered branch, or perhaps a laundered branch with a quilt patch addition commit. -- cgit v1.2.3