On Wed, Feb 01, 2017 at 12:42:38PM +0000, Barak A. Pearlmutter wrote: > Okay. I'm including a diff from 2.0-3 to the debian/* subdir below. > I'm sending a tarball of an upstream snapshot (commit 6fe2f4f) under > separate cover without a BTS CC, because it seems silly to include it > as an attachment. I am however including below a log of the nontrivial > upstream commits, along with file change histograms, so you can see > what's what.
You're missing the point here - the problem here is having to do some combination of reverse engineering the diff and fiddling through the git history to extract individual, reviewable changes so I can find out what happened. If the package were maintained in git this would work a lot better but it's not so I've just got this big lump that's been thrown over the wall at me. > BTW, this kind of thing is really easy w/ git, each of the above is a > single short command. Github also exports snapshots as tarballs at > some magic URLs. If you need anything like that in the future just let > me know. I'm more than familiar with git.
signature.asc
Description: PGP signature
