> > src/mesa/glapi/ and windows/VC6/mesa/ ) exist in upstream git, but not > > in the upstream release. I guess they are there by mistake, maybe the > > diff was made between a git-based tree and the upstream released tree? > > > Yes, the package is built from git, so files which are in git but not in > the tarballs end up in the debian diff. Why is that a problem?
No practical problem I guess, but it doesn't look right :) If upstream had a reason for stripping these things out of the release, why should we put them back? Isn't there a practice of keeping diffs as small and clean as possible? But I understand that the Debian git is tracking upstream git during development, and that it might mean extra work to filter out these files. Would it work to make the diff against the git head of the release, and then use this diff against the released tarballs? Supposing that we haven't touched these files in question, they would not appear then. Tormod -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
