X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=git-debrebase.5.pod;h=d39ad9484986fb022e98e735a030d91f6e136063;hp=cc9fb7a03e3edf77b1d268cfd9ae697d95c0af3b;hb=96768306c386add902ee7a8b733225e9d811b971;hpb=472edf9ca063494baf017ed891baa34d0ac057be diff --git a/git-debrebase.5.pod b/git-debrebase.5.pod index cc9fb7a0..d39ad948 100644 --- a/git-debrebase.5.pod +++ b/git-debrebase.5.pod @@ -29,6 +29,11 @@ provided by your upstream. However, use of git-debrebase in Debian does not make anything harder for derivatives, and it can make some things easier. +When using gitk on branches managed by git-debrebase, +B, B +and B (or B) +produce more useful output than the default. + =head1 TERMINOLOGY =over @@ -482,6 +487,48 @@ These patch files can be stripped out and/or regenerated as needed. =back +=head1 ILLEGAL OPERATIONS + +Some git operations are not permitted in this data model. +Performing them will break git-debrebase. + +=over + +=item General merges + +See L, above. + +=item git-rebase starting too soon, or without base argument + +git-rebase must not be invoked in such a way that +the chosen base is before the anchor, +or before the last pseudomerge. +This is because git-rebase mangles merges. +git rebase --preserve-merges is also dangerous. + +git-rebase without a base argument will often start too early. + +For these reasons, +it is better to use git-debrebase and +let it choose the base +for your rebase. +If you do realise you have make this mistake, +it is best to use the reflog to recover to a suitable +good previous state. + +=item Editing debian/patches + +debian/patches is an output from git-debrebase, +not an input. +If you edit patches git-debrebase will complain +and refuse to work. +If you add patches your work is likely to be discarded. + +Instead of editing patches, +use git-debrebase to edit the corresponding commits. + +=back + =head1 COMMIT MESSAGE ANNOTATIONS git-debrebase makes annotations