chiark / gitweb /
git-debrebase: Actually avoid read-tree in walk when not rewriting
authorIan Jackson <ijackson@chiark.greenend.org.uk>
Sun, 19 Aug 2018 15:44:56 +0000 (16:44 +0100)
committerIan Jackson <ijackson@chiark.greenend.org.uk>
Sun, 19 Aug 2018 16:46:00 +0000 (17:46 +0100)
commite64f34c55170943aa35bb806700c8ba3e99c50a7
treed45dcff29e6f34aff97982363820b1ebff83dfeb
parentb39329c0ead53a3f51ed7c7fa946a79ff9463f18
git-debrebase: Actually avoid read-tree in walk when not rewriting

See
   git-debrebase: Prep for avoid read-tree in walk when not rewriting
for the motivation.

Here we try to check that the commit we would make, if we were
actually calling read-tree, write-tree and hash-object, would be
identical to the one we are reusing.

In particular, we check that the upstream files, and the debian/
directory, have the contents we would feed to read-tree.  And we check
that the parent list is the same.

With these checks this new algorithm is, I think, safe enough to just
use always.   So set $opt_careful to 0.  We will abolish this
variable in a moment.

Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
debian/changelog
git-debrebase