I have faced similar issues at times. If you like everything about the
current behavior of AFS aside from the impact it can have on git you might
attack it from the git side. Maybe there is a way to stop git from
recursing all the way to /afs/ ? Similar solutions have worked for me with
things
I second the inclusion of an explicit way of requesting one behavior or the
other. As long as I have a way to explicitly specify both behaviors working
around the change in anything that wraps the pts command should be simple
enough.
I think I prefer the new behavior you are suggesting as the
