From: Jeff King <peff@peff.net>
To: "Ciprian Dorin, Craciun" <ciprian.craciun@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: Git push failure in the case of SSH to localhost
Date: Wed, 11 Feb 2009 14:22:45 -0500 [thread overview]
Message-ID: <20090211192245.GA28832@coredump.intra.peff.net> (raw)
In-Reply-To: <8e04b5820902111120w4cb87b41sfca647a838bab43c@mail.gmail.com>
On Wed, Feb 11, 2009 at 09:20:51PM +0200, Ciprian Dorin, Craciun wrote:
> 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...)
I don't see what is per-repo about that. That is, why not put it in a
PATH directory accessible by all repos. And if there is some
repo-specific data, you can have the script read it from the current
repo by "git config".
-Peff
next prev parent reply other threads:[~2009-02-11 19:24 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 [this message]
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
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=20090211192245.GA28832@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=ciprian.craciun@gmail.com \
--cc=git@vger.kernel.org \
--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).