X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=NOTES.git-debrebase;h=79b6f2b60b83cfd76a2d3b051edfb9b318f3ca78;hp=09237d5973cda501e24ecb4acb4b73c7e4a45a51;hb=75d0b8d7275c035f76db79e7cf7e802e061a9bee;hpb=ac6f8cf1df126cf79e08d431932b76cec83f443a diff --git a/NOTES.git-debrebase b/NOTES.git-debrebase index 09237d59..79b6f2b6 100644 --- a/NOTES.git-debrebase +++ b/NOTES.git-debrebase @@ -1,6 +1,5 @@ TODO reference docs - git-debrebase(5) data model git-debrebase(1) command line tutorial dgit-maint-debrebase(7) @@ -10,42 +9,6 @@ TODO arrange for dgit to automatically stitch on push -======================================= - -special commit tags -overall format - [git-debrebase[ COMMIT-TYPE [ ARGS...]]: PROSE, MORE PROSE] - -[git-debrebase: split mixed commit, debian part] -[git-debrebase: split mixed commit, upstream-part] -[git-debrebase: convert dgit import, debian changes] -[git-debrebase anchor: convert dgit import, upstream changes] - -[git-debrebase upstream-combine . PIECE[ PIECE...]: new upstream] -[git-debrebase anchor: new upstream NEW-UPSTREAM-VERSION, merge] -[git-debrebase: new upstream NEW-UPSTREAM-VERSION, changelog] - -[git-debrebase convert-from-gbp: drop patches] -[git-debrebase anchor: declare upstream] -[git-debrebase pseudomerge: stitch] - -[git-debrebase convert-to-gbp: commit patches] - -m{^\[git-debrebase (?:\w*-)?upstream combine \.((?: $extra_orig_namepart_re)+)\]} - -Every anchor commit must be a merge. In principle, this is not -necessary. After all, we are relying on the - [git-debrebase anchor: ...] -commit message annotation in "declare" anchor merges (which -do not have any upstream changes), to distinguish those anchor -merges from ordinary pseudomerges (which we might just try to strip). - -However, the user is going to be doing git-rebase a lot. We really -don't want them to rewrite an anchor commit. git-rebase -trips up on merges, so that is a useful safety catch. - -======================================= - workflow git-debrebase blah [implies start] strips pseudomerge(s) @@ -121,27 +84,6 @@ We check we are ff from remotes before recording new ffq-prev ---------- now follows much the same info in different words ---------- -1. git-debrebase [-i etc.] - - should: - check for ffq-prev - if is already a ffq-prev, fine, do no more - if not: - - check our origin branch exists and we are ff from it - if not fail - - check our other might-be-pushed to branches - check we are ff from them - if not fail - - set ffq-prev to something which is ff from - all above branches - - we use our tip, as discussed above - (optionally, can use some other commit which is ff - from all of the above, eg one of them) - N. git-debrebase [--noop-ok] record-ffq-prev does what is described above