Accepted:
kernel-headers-2.6.11-1-386_2.6.11-2_i386.deb
  to 
pool/main/k/kernel-image-2.6.11-i386/kernel-headers-2.6.11-1-386_2.6.11-2_i386.deb
kernel-headers-2.6.11-1-686-smp_2.6.11-2_i386.deb
  to 
pool/main/k/kernel-image-2.6.11-i386/kernel-headers-2.6.11-1-686-smp_2.6.11-2_i386.deb
kernel-headers-2.6.11-1-686_2.6.11-2_i386.deb
  to 
pool/main/k/kernel-image-2.6.11-i386/kernel-headers-2.6.11-1-686_2.6.11-2_i386.deb
kernel-headers-2.6.11-1-i386_2.6.11-2_i386.deb
  to 
pool/main/k/kernel-image-2.6.11-i386/kernel-headers-2.6.11-1-i386_2.6.11-2_i386.deb
kernel-headers-2.6.11-1-k7-smp_2.6.11-2_i386.deb
  to 
pool/main/k/kernel-image-2.6.11-i386/kernel-headers-2.6.11-1-k7-smp_2.6.11-2_i386.deb
kernel-headers-2.6.11-1-k7_2.6.11-2_i386.deb
  to 
pool/main/k/kernel-image-2.6.11-i386/kernel-headers-2.6.11-1-k7_2.6.11-2_i386.deb
kernel-headers-2.6.11-1_2.6.11-2_i386.deb
  to 
pool/main/k/kernel-image-2.6.11-i386/kernel-headers-2.6.11-1_2.6.11-2_i386.deb
kernel-image-2.6.11-1-386_2.6.11-2_i386.deb
  to 
pool/main/k/kernel-image-2.6.11-i386/kernel-image-2.6.11-1-386_2.6.11-2_i386.deb
kernel-image-2.6.11-1-686-smp_2.6.11-2_i386.deb
  to 
pool/main/k/kernel-image-2.6.11-i386/kernel-image-2.6.11-1-686-smp_2.6.11-2_i386.deb
kernel-image-2.6.11-1-686_2.6.11-2_i386.deb
  to 
pool/main/k/kernel-image-2.6.11-i386/kernel-image-2.6.11-1-686_2.6.11-2_i386.deb
kernel-image-2.6.11-1-k7-smp_2.6.11-2_i386.deb
  to 
pool/main/k/kernel-image-2.6.11-i386/kernel-image-2.6.11-1-k7-smp_2.6.11-2_i386.deb
kernel-image-2.6.11-1-k7_2.6.11-2_i386.deb
  to 
pool/main/k/kernel-image-2.6.11-i386/kernel-image-2.6.11-1-k7_2.6.11-2_i386.deb
kernel-image-2.6.11-i386_2.6.11-2.dsc
  to pool/main/k/kernel-image-2.6.11-i386/kernel-image-2.6.11-i386_2.6.11-2.dsc
kernel-image-2.6.11-i386_2.6.11-2.tar.gz
  to 
pool/main/k/kernel-image-2.6.11-i386/kernel-image-2.6.11-i386_2.6.11-2.tar.gz
Announcing to debian-devel-changes@lists.debian.org


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to