Re: [kernel.org users] README and ChangeLog files

From: Junio C Hamano <junio@pobox.com>
Date: Aug 22, 2008, 21:13 UTC
Message-ID: <7vej4g92io.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <20080822082908.GA29475@isilmar.linta.de>

Dominik Brodowski <linux@dominikbrodowski.net> writes:

Show 12 quoted lines

> On Thu, Aug 21, 2008 at 04:20:25PM -0700, Junio C Hamano wrote:
>> Yes, and the fact that it is not "git-foo" that was deprecated, but
>> running the dashed-form without adjusting PATH was, makes it impractical
>> to issue warning messages before the transition actually happened.
>
> So I can safely ignore the warning in the release notes which states
>
> | but users are again strongly encouraged to adjust their
> | scripts to use "git xyzzy" form, as we will stop installing
> | "git-xyzzy" hardlinks for built-in commands in later releases.
>
> ?

No. What the above means is that the deprecation and removal of git-foo for builtins (such as "git commit") are not done in 1.6.0, but it will eventually happen. So your two choices are:

 (1) stop using dashed form "git-foo" and replace them with "git foo" form
     everywhere in your script now and won't worry about this anymore; or

 (2) add this to the beginning of your existing scripts:

     PATH=$(git --exec-path):$PATH

     and later do (1) when you have time.

But if you choose to do the latter, please do so after promising that you won't complain like this time everybody did, saying "Oh, I knew it was coming but I have postponed doing it for a long time because it continued to work" ;-)

[jc: git list cc'ed]

Maybe we should try to see how hard it would be to issue warnings when "git-foo" form is used for builtins before we declare that dashed form is deprecated for builtins, and start warning when the deprecation actually happens. As many people on this thread suggested, it would make the transition easier.