Package: pristine-tar Version: 0.9 Severity: wishlist The current way pristine-tar stores information doesn't prevent the object which sha1 is in the .tar.gz.id file in a given pristine-tar commit-tree to be removed by git-prune, if, for whatever reason, the object is orphaned (a stupid example would be commit message change in the upstream branch with git filter-branch).
I would suggest two possible solutions: - have the delta stored in the commit message (possibly in base64 form) and the commit-tree be the upstream tree sha1. - replace the .tar.gz.id file by a directory which sha1 would just be the upstream tree sha1. If that is not clear enough, please ping me. Mike -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages pristine-tar depends on: ii libc6 2.7-8 GNU C Library: Shared libraries ii perl-modules 5.8.8-12 Core Perl modules ii xdelta 1.1.3-8 A diff utility which works with bi ii zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime Versions of packages pristine-tar recommends: ii bzip2 1.0.4-3 high-quality block-sorting file co ii pbzip2 1.0.2-0 parallel bzip2 implementation -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
