git-* commands in /usr/libexec/git-core/

Nicolas Troncoso ntroncos at gmail.com
Wed Jan 7 13:41:38 UTC 2009


On Wed, Jan 7, 2009 at 10:35 AM, Jeffrey Ollie <jeff at ocjtech.us> wrote:
> On Wed, Jan 7, 2009 at 4:21 AM, Bryn M. Reeves <bmr at redhat.com> wrote:
>>
>> I guess it depends how much we care about being close to upstream for this.
>> If it's worth the effort to move these to libexec, then perhaps putting
>> compatibility symlinks in place for a couple of releases (with a clear
>> relnote that they will be removed in a future release and scripts need
>> updating) could be a way to handle the transition?
>
> Adding symlinks does nothing to help, it just delays the pain because
> people won't read the release notes or won't bother to fix their
> scripts until the symlinks disappear.  Fixing the scripts is trivial,
> and backwards compatible to boot.

I fully agree with jeff in this topic. In my expirience when you get
"temporal" basis fixes in they turn out to be permanent. Rawhide
users should feel the pain and get them fixed, the sooner the better.

cheers

-- 
Nicolás Troncoso Carrère




More information about the devel mailing list