X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=NOTES.git-debrebase;h=6a731f19cc1b0830783348c85c26e8dacb4ab4cb;hp=4d7cf20f26912c40babad44d646d5832b31612f5;hb=6f9e94728e55a5d52120760e6451e9ba48648051;hpb=e6c5fe85824337be49d77f89aa388c82361784e4 diff --git a/NOTES.git-debrebase b/NOTES.git-debrebase index 4d7cf20f..6a731f19 100644 --- a/NOTES.git-debrebase +++ b/NOTES.git-debrebase @@ -174,6 +174,47 @@ so that the overall result will be series of pseudomerges. ======================================== +So, pm handling specifics: + +strategy is to avoid making needless pseudomerges +pseudomerges that exist will be preserved +(by being included in will-overwrite) + +This is good because the presence of a pseudomerge means we know we +want to keep it; and that allows explicit control over history detail +level. + +It does mean we must avoid making the pseudomerges unnecessarily. +They should be made just before (ideally, part of) dgit push. + +1. git-debrebase [-i etc.] + + should: + check for will-overwrite + if is already a will-overwrite, 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 will-overwrite 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) + +2. git-debrebase stitch + + makes pseudomerge with will-overwrite + deletes will-overwrite + +======================================== + import from gbp [ all this is done now: @@ -202,3 +243,6 @@ 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 + +should this be called import or gbp2debrebase as it is now ? +gbp uses "import" oddly but I'm tempted to use it normally here.