On 2006-11-07, at 15:10 EST, P T Withington wrote:
On 2006-11-07, at 14:48 EST, Benjamin Shine wrote:
On Nov 7, 2006, at 7:50 AM, P T Withington wrote:
Comments:
1) Your editor apparently sticks lots of attributes into text
files, and your tar bundles them up as ._<filename>. Just an
annoyance, I guess, but it would be nice to teach your tar to not
bother with these attributes for the purposes of review. (What
tar are you using?)
I'm using GNU tar in /usr/bin/tar... educating it would require
changing svn-bash.sh. I'll try a change locally, and see if it
fixes this without breaking other things. (I'm concerned about the
chance of mucking things up when adding exclusions that start with
the potentially regexp-meaningful "._")
I'm using the same, so something else is going on. I'm not sure
that filtering for ._ will have any effect; I am suspicious that
this is a fictitious file name that represents the second fork of a
Mac file. It probably gets written for any file that has more than
one fork. We may not have seen it before because the editors we
use don't write any meta information into text files....
Hah! Just happened to me. I decided to switch over to using
Aquamacs, which has a nifty feature to write 'creator codes' on each
file you edit with it (so you can double-click on the file and have
it open in Aquamacs). This creates the ._ files that tar then
graciously picks up for you. Bleah.
I turned that off in my editor. You can turn off something like
'Save Document State' in BBEdit to effect the same. Don't know about
other editors. Don't know if there is an option on tar to ignore
resource forks on certain file types...
