Re: GIT - breaking backward compatibility

From: Petr Baudis <pasky@suse.cz>
Date: Sep 22, 2005, 14:41 UTC
Message-ID: <20050922144124.GJ21019@pasky.or.cz>
In-Reply-To: <7vpsr4cx0f.fsf@assigned-by-dhcp.cox.net>

Dear diary, on Tue, Sep 20, 2005 at 04:07:28AM CEST, I got a letter where Junio C Hamano <junkio@cox.net> told me that...

Show 6 quoted lines

>  * Tools renaming plan calls for removal of the backward
>    compatible command names (e.g. git-fsck-cache and
>    git-update-cache) sometime in the future.  This is scheduled
>    for 0.99.8 around beginning of October.  If somebody wants
>    extended amnesty period, this can be pushed back but unless I
>    hear otherwise...

Actually, could we please keep the old git-ssh-* stuff for a bit (perhaps a lot) longer? The other renames are fine because people usually keep their git-core and porcelain versions in sync, but the git-ssh-* stuff is about network interoperability and you are forcing other people to upgrade their installations, which may be troublesome for them in the case their distribution didn't package the new stuff yet or whatever. It's just two commands after all, so could we please have them for at least another month or so?

Thanks,

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.