Re: Git push failure in the case of SSH to localhost

[Junio C Hamano <gitster@pobox.com>]

"Ciprian Dorin, Craciun" <ciprian.craciun@gmail.com> writes:

>     I'll merge both Junio's and Jeff's emails into one... My answers bellow.
>
> On Wed, Feb 11, 2009 at 9:40 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> "Ciprian Dorin, Craciun" <ciprian.craciun@gmail.com> writes:
>>
>>> On Wed, Feb 11, 2009 at 9:27 PM, Junio C Hamano <gitster@pobox.com> wrote:
>>>
>>>> And why isn't it in $HOME/bin/?
>>>
>>>     No, it is inside .git/bin folder.
>>
>> You are not answering my question.
>>
>> I questioned the sanity of putting the scripts in .git/bin/ per
>> repository.  Why shouldn't a useful script like your "branch-import"
>> available to _all_ your repositories, possibly taking customization per
>> repository from repository's .git/config file, so that it does what is
>> appropriate in each repository?
> ...
>     Both these solutions work fine, except one concern: when moving
> the repository I would also want to move my scripts,...

Define "moving the repository".  More often than not, people move their
repositories with "git clone" than "tar cf - | tar xf -".

No matter how you are moving it to a new location, you would want to have
a working set of "regular environment" you normally work in.  Why aren't
you moving/copying your $HOME/bin at the same time to get a more familiar
and useful environment?  Viewed under this light, I think your "I move my
repository to a new machine" is a made up example that is not interesting
at all, if you ask me.

There are additional security implications.  You can invite a victim to
run "git diff" in your repository which runs your .git/bin/git-diff, for
example.