Re: [PATCH] remote-helpers: point at their upstream repositories

From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: May 18, 2014, 17:34 UTC
Message-ID: <vpqk39jous5.fsf@anie.imag.fr>
In-Reply-To: <5377994fe8dec_7a27d4b30438@nysa.notmuch>

Felipe Contreras <felipe.contreras@gmail.com> writes:

Show 5 quoted lines

>  % git fetch
>  WARNING: git-remote-hg is now maintained independently.
>  WARNING: For more information visit https://github.com/felipec/git-remote-hg
>  searching for changes
>  no changes found

I don't think the situation is as simple as you claim. In many cases, the first step before the ones you are mentionning are:

  cd $git/contrib/remote-helpers
  cp git-remote-{hg,bzr} somewhere/in/path

They produces no warning if git-remote-{hg,bzr} exist with the warning, but "no such file or directory: contrib/remote-helpers" if the directory has been renamed or removed.

When git-remote-{hg,bzr} are installed with a package manager, the fact that they are part of Git's core or not is often irrelevant. For example, Debian splits the git.git source into many packages, so a Debian user will not see any difference between helpers included in git.git or outside (e.g. I have to install the package git-svn if I want to use git-svn).

That said, I'm fine with the "add a warning" option too.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/