On Thu, 2008-08-28 at 03:33 -0700, Perry Wagle wrote: > Are you suggesting that I break into machines that I don't have access > to add a export PATH= line to copies of scripts that were written 6 > months ago, and worked just fine until someone decided that "upward > compatibility" wasn't an important concept? Not at all. But as long as you also refrain from breaking into those same machines and upgrading them to git 1.6.0, you should be fine. Or if you _do_ upgrade them to git 1.6.0, you should make sure you build with gitexecdir=/usr/bin to prevent the breakage. What distribution are you running on those machines? If they upgrade their version of git from an earlier version to 1.6.0 in a stable release without setting gitexecdir=/usr/bin to preserve compatibility, then the packager needs to be taken out back and shot. Perhaps you should file a bug in advance, to make sure they're aware of the issue and make sure that if/when they update to 1.6.0, they set gitexecdir properly. -- David Woodhouse Open Source Technology Centre David.Woodhouse@xxxxxxxxx Intel Corporation -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
