git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ciprian Dorin, Craciun" <ciprian.craciun@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	Jeff King <peff@peff.net>,
	git@vger.kernel.org
Subject: Re: Git push failure in the case of SSH to localhost
Date: Wed, 11 Feb 2009 21:34:07 +0200	[thread overview]
Message-ID: <8e04b5820902111134o73f0cbc9gc25aeaae9a267f9a@mail.gmail.com> (raw)
In-Reply-To: <7vd4doepvb.fsf@gitster.siamese.dyndns.org>

On Wed, Feb 11, 2009 at 9:27 PM, Junio C Hamano <gitster@pobox.com> wrote:
> "Ciprian Dorin, Craciun" <ciprian.craciun@gmail.com> writes:
>
>> On Wed, Feb 11, 2009 at 9:14 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
>>> "Ciprian Dorin, Craciun" <ciprian.craciun@gmail.com> wrote:
>>>>
>>>>     Here is what I'm trying to accomplish: I want to add to the git
>>>> search path also the folder ${GIT_DIR}/bin if this already exists...
>>>> (This allows me to have repository specific commands...)
>>>
>>> for f in `cd $(git rev-parse --git-dir)/bin && ls *`; do
>>>  git config alias.$f '!$(git rev-parse --git-dir)/bin/'$f
>>> done
>>>
>>> No need to patch git.
>>>
>>> --
>>> Shawn.
>>
>>     :) Yes I know about the alias trick...
>>
>>     But I find it easier to just create a bin folder and drop my
>> scripts there... (For example git-branch-import that takes a new
>> branch name and an URL and creates the branch with no ancestry and
>> knows http, ftp, svn, tar.{gz,bz2}, zip, etc...)
>
> And why isn't it in $HOME/bin/?

    No, it is inside .git/bin folder. I like to think to my bin folder
like the hooks folder... This way when I move a repository I move the
hooks and the specific commands.

    Ciprian.

  reply	other threads:[~2009-02-11 19:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 16:24 Git push failure in the case of SSH to localhost Ciprian Dorin, Craciun
2009-02-11 18:05 ` Jeff King
2009-02-11 18:42   ` Ciprian Dorin, Craciun
2009-02-11 18:44     ` Jeff King
2009-02-11 19:03       ` Ciprian Dorin, Craciun
2009-02-11 19:14         ` Shawn O. Pearce
2009-02-11 19:20           ` Ciprian Dorin, Craciun
2009-02-11 19:22             ` Jeff King
2009-02-11 19:32               ` Ciprian Dorin, Craciun
2009-02-11 19:42                 ` Jeff King
2009-02-11 20:03                   ` Ciprian Dorin, Craciun
2009-02-11 20:23                     ` Junio C Hamano
2009-02-11 20:49                       ` Ciprian Dorin, Craciun
2009-02-11 21:03                         ` Johannes Schindelin
2009-02-11 19:27             ` Junio C Hamano
2009-02-11 19:34               ` Ciprian Dorin, Craciun [this message]
2009-02-11 19:40                 ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8e04b5820902111134o73f0cbc9gc25aeaae9a267f9a@mail.gmail.com \
    --to=ciprian.craciun@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).