X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=NOTES.git-debrebase;h=09237d5973cda501e24ecb4acb4b73c7e4a45a51;hb=8bce000d9c9af3912aeefe1f3874ce3b125cae04;hp=97038733dca16ae3337a2a29c1e7a41be0be21ab;hpb=8872ad84313c7a9175c7dfbd63b4c94bc4df6d51;p=dgit.git diff --git a/NOTES.git-debrebase b/NOTES.git-debrebase index 97038733..09237d59 100644 --- a/NOTES.git-debrebase +++ b/NOTES.git-debrebase @@ -6,14 +6,10 @@ TODO dgit-maint-debrebase(7) someone should set branch..mergeOptions to include --ff-only ? - clean up remains of NOTES and README + clean up remains of README arrange for dgit to automatically stitch on push -======================================== - -# refs/ffq-prev/REF relates to refs/REF - ======================================= special commit tags @@ -72,6 +68,8 @@ workflow Theory for ffq-prev + refs/ffq-prev/REF relates to refs/REF + When we strip a pm, we need to maybe record it (or something) as the new start point. @@ -155,6 +153,10 @@ N. git-debrebase [--noop-ok] record-ffq-prev we will teach dgit to do git-debrebase stitch + or some such ? + +following parts are not implemented and maybe aren't the +best subcommand names etc. 3. git-debrebase push @@ -166,41 +168,16 @@ N. git-debrebase [--noop-ok] record-ffq-prev stiches, finalises changelog, signs tags, pushes everything for the future, when there is some automatic builder -ffq-prev for each ref - refs/heads/FOO -is - refs/ffq-prev/FOO - ======================================== import from gbp -[ all this is done now: - inputs: - current HEAD (patches-unapplied), - this is going to be the base of the old breakwater - nominated upstream - - checks: - HEAD: = upstream: - upstream..HEAD: 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 - anchor merge 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 +that is what is currently implemented ======================================== @@ -244,6 +221,8 @@ current avaiable strategies: ======================================== +For downstreams of Debian, sketch of git-ffqrebase + # git-ffqrebase start [BASE] # # records previous HEAD so it can be overwritten # # records base for future git-ffqrebase