X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=NOTES.git-debrebase;h=b4ffdda23e760a98b165873470d9b8b6c4967f72;hp=a8e16aff41eda9230a57f76f9f39471fdf3acf28;hb=7faed22010cacb9bd7cc029b860840947e03bf8a;hpb=3d90aa0ebc9d1a48dc7300572fbd58311e0d0ef1 diff --git a/NOTES.git-debrebase b/NOTES.git-debrebase index a8e16aff..b4ffdda2 100644 --- a/NOTES.git-debrebase +++ b/NOTES.git-debrebase @@ -1,5 +1,4 @@ TODO - more tests, see "todo" in gdr-editw reference docs git-debrebase(5) data model git-debrebase(1) command line @@ -45,27 +44,29 @@ overall format [git-debrebase: split mixed commit, debian part] [git-debrebase: split mixed commit, upstream-part] [git-debrebase: convert dgit import, debian changes] -[git-debrebase breakwater: convert dgit import, upstream changes] +[git-debrebase anchor: convert dgit import, upstream changes] [git-debrebase upstream-combine . PIECE[ PIECE...]: new upstream] -[git-debrebase breakwater: new upstream NEW-UPSTREAM-VERSION, merge] +[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 breakwater: declare upstream] +[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 breakwater commit must be a merge. In principle, this is not +Every anchor commit must be a merge. In principle, this is not necessary. After all, we are relying on the - [git-debrebase breakwater: ...] -commit message annotation in "declare" breakwater merges (which -do not have any upstream changes), to distinguish those breakwater + [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 a breakwater base commit. git-rebase +don't want them to rewrite an anchor commit. git-rebase trips up on merges, so that is a useful safety catch. @@ -266,7 +267,7 @@ import from gbp new breakwater is old HEAD commit to remove d/patches - breakwater pseudomerge with upstream + anchor merge with upstream "rebase" of pq branch, each commit with d/patches stripped ]