> would it be ok to label the tracks: > > GD93-08-22d1t1 > GD93-08-22d1t2 > etc. > > and make the change in the MD5 also (of course) before > I send it off to my recipient, or am I just being anal. > The MD5 digest will still be untouched, I just want to > change the labeling convention.
Absolutely, positively... In fact, you'll be doing a service to your recipient and subsequent recipients of this show. What matters in an md5 file is the checksums, not the file names. You should not use a file compare to determine if your show matches the DB, but should rather manually look at the checksums and see if they are the same. (You only need to check the 1st few characters to tell that.) I have seen a few multiple listings in the DB where the only difference was the file naming convention; personally, I see no reason for the multiple listings. > I want to get this in the mail in the next hour. Sorry I didn't read this until the morning. Gift tax - I'd like to offer a few PASV uploads of one of the following to anyone who can pull at least 20KB/s. gd83-10-11 gd83-10-15 gd90-06-09 jgb89-09-16 The requirements are pretty simple: 1. You must send your request to [EMAIL PROTECTED]; do not reply to this address. 2. You must be able to accept a PASV transfer and pull 20KB/s. 3. Offer to spread this to others. 4. Repeat rule 1. Send IP & l/p. I won't be able to start uploading until tomorrow. 5. Duh Charles _______________________________________________ etree.org etree mailing list <[EMAIL PROTECTED]> http://mail.etree.org/mailman/listinfo/etree Need help? Ask <[EMAIL PROTECTED]>
