X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=README.git-debrebase;h=19ddbc05863d5fa3231b8494a6d3dbacce4a0dff;hp=8dcb0df4d165b641d070c1b2c2bfd2be393e8e2f;hb=47e5e2edc83917f5e21e00586a0907c1f641f174;hpb=d0a2fee062d2c79e9019fdebd96796d8b3ad6d5f diff --git a/README.git-debrebase b/README.git-debrebase index 8dcb0df4..19ddbc05 100644 --- a/README.git-debrebase +++ b/README.git-debrebase @@ -1,78 +1,122 @@ -From: Ian Jackson -To: Sean Whitton -Cc: debian-devel@lists.debian.org -Subject: Re: Feedback on 3.0 source format problems -Date: Fri, 6 Jan 2017 15:29:38 +0000 -Sean Whitton writes ("Re: Feedback on 3.0 source format problems"): -> Could you explain in general terms the difference between the -> interchange and packaging-only branches -See modified diagram below. Are the annotations I have added (and the -name change) any help ? +So it would be possible to write a `git-debrebase' tool which would +take (for example) B4, above, and be able to perform functions like: + + * Strip pseudomerges: Rewrite the current branch so it contains no + pseudomerges, turning ...B3 into ...@-A-1-2-B3. (This should + make a note, in your .git/ somewhere, of the original branch + tip so that it can be overwritten with a pseudomerge.) + + * Cleanup branch: Reorganise the current branch so that the debian/ + changes come first, turning -@-A-1-2-B3 into ...@-A-B-1-2-3. + + * New upstream rebase: Start rebasing onto a new upstream version, + turning ...#..@-A-B-1-2-3 into (...#..@-A-B-|...#'-)@'-1-2. This + would be a wrapper around git-rebase, which prepares @' and then + tries to rebase 1 2 onto @'. So if you ask for an interactive + rebase @' doesn't appear in your commit list. + + Note that the construction of @' cannot fail because @' simply + copies debian/ from B and and everything else from #'. (Rebasing A + and B is undesirable. We want the debian/ files to be non-rebasing + so we can `git log' and get the packaging history.) -> Does the packaging-only branch contain debian/ alone? + * Record pseudomerge. This is like "committing" your patch queue. + The LH parent is taken from the previously recorded tip. (We could + perhaps check that this is consistent with what we see in + debian/changelog, but that is not a sufficient check so the + recorded tip check is primary.) + +Maybe some of these operations should automatically edit +debian/changelog. + + +Sean Whitton writes ("Re: Feedback on 3.0 source format problems"): +> Does the [breakwater] branch contain debian/ alone? No, it also contains a complete unmodified copy of the upstream code. (Except that if upstream had a debian/ directory, it is completely -replaced.) Perhaps this is the wrong name. Let's try -`merging-baseline' - -For `3.0 (quilt)' the merging-baseline branch contains roughly what -you would get if you untarred the origs and the debian.tar.gz, and -then deleted all the patches without applying them. - -Not shown on the diagram is the commit `add patch queue to -debian/patches', which would be needed for `3.0 (quilt)'. This is -because the diagram is in terms of a sane source format, not `3.0 -(quilt)'. For use with quilty sources, there would be such a commit -(probably dgit-generated) on top of the actual upstream change -commits: - - ------/--A!----/--B3!--%--/--> interchange view - / / / with debian/ directory - % % % all upstream changes applied - / / / 3.0 (quilt) has debian/patches - / 2* 2* - / / / - 2* 2 2 - / / / - 1 1 1 `merging-baseline' branch - / / / unmodified upstream code - ---p-----p--A----p--B--C--> plus debian/ (but no debian/patches) - / / / - --#-----#-------#-----> upstream - - Key: - - 1,2,3 commits touching upstream files only - A,B,C commits touching debian/ only - B3 mixed commit (eg made by an NMUer) - # upstream releases - - -p- special merge, takes contents of debian/ from the - / previous `merging-baseline' commit and rest from upstream - - -/- pseudomerge; contents are identical to - / parent lower on diagram. - - % dgit-generated commit of debian/patches. - `3.0 (quilt)' only; dropped by rebase tool. - - * Maintainer's HEAD was here while they were editing, - before they said they were done, at which point their - tools generated [% and] -/- commit[s] to convert to - the fast-forwarding interchange branch. (Maybe the - tooling is simply `dgit push'.) - - ! NMUer's HEAD was here when they said `dgit push'. - Rebase branch launderer turns each ! into an - equivalent *. - -Ian. - --- -Ian Jackson These opinions are my own. - -If I emailed you from an address @fyvzl.net or @evade.org.uk, that is -a private address which bypasses my fierce spamfilter. +replaced.) + +For `3.0 (quilt)' the breakwater branch contains roughly what you +would get if you untarred the origs and the debian.tar.gz, and then +deleted all the patches without applying them. + + +dgit import handling +-------------------- + +Consider a non-dgit NMU followed by a dgit NMU: + + + + interchange --/--B3!--%--/----D*--> + / / + % 4 + / 3 + / 2 + / 1 + 2* &_ + / /| \ + 1 0 00 =XBC% + / + / + --@--A breakwater + / + --#--------> upstream + + + Key: + + =XBC% dgit tarball import of .debian.tar.gz containing + Debian packaging including changes B C and patches + + 0 dgit tarball import of upstream tarball + 00 dgit tarball import of supplementary upstream tarball + &_ dgit nearly-breakwater import + &' git-debrebase converted import (upstream files only) + D' git-debrebase converted debian/ changes import + + * ** before and after HEAD + +Want to transform this into: + + I. No new upstream version (0 + 00 eq #) + + --/--B3!--%--/------D*-------------/--> + / / / + % 4 4** + / 3 3 + / 2 2 + / 1 1 + 2* &_ / + / /| \ / + 1 0 00 =XBC% / + / / + / / + --@--A-----B-----------------------C--D + / + --#-----------------------------------------> + + + II. New upstream (0 + 00 neq #) + + --/--B3!--%--/------D*-------------/--> + / / / + % 4 4** + / 3 3 + / 2 2 + / 1 1 + 2* &_ / + / /| \ / + 1 0 00 =XBC% / + / / + / / + --@--A-----B--------------------@--C--D + / / + --#----------------------- - - / - - -----> + / + &' + /| + 0 00