From: Peter Krefting <peter@softwolves.pp.se>
To: Git <git@vger.kernel.org>
Subject: [PATCH 0/2] RFC: Better handling of git init remote-spec
Date: Fri, 12 Nov 2010 12:31:44 +0100 [thread overview]
Message-ID: <cover.1289561504.git.peter@softwolves.pp.se> (raw)
>From time to time I forget myself and try to initialize a repository on a remote
machine by writing something like
git init --bare remote.machine:myrepo.git
just to get a local directory called "remote.machine:myrepo.git" set up.
Or, even worse, a
git init --bare ssh://remote.machine/myrepo.git
These patches try to fix this. The first patch tries to detect if a remote
repository specification was supplied, and just stop with an error message.
That one is fairly safe.
The second one I haven't got working yet, but I have the beginnings of a
patch that actually tries to run "git-init" on the remote repository. Any
ideas on how to get this actually working (it should be possible for the
"ssh" transport at least) are welcome.
Peter Krefting (2):
Detect attempts at calling git init specifying a remote repository.
WIP: Allow running git init on a remote repository specification.
builtin/init-db.c | 16 +++++++++++++++-
remote.c | 11 +++++++++++
remote.h | 1 +
3 files changed, 27 insertions(+), 1 deletions(-)
--
1.7.3
next reply other threads:[~2010-11-12 11:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 11:31 Peter Krefting [this message]
2010-11-12 11:27 ` [PATCH 1/2] [RFC] Detect attempts at calling git init specifying a remote repository Peter Krefting
2010-11-16 17:57 ` Junio C Hamano
2010-11-16 20:10 ` Peter Krefting
2010-11-12 11:30 ` [PATCH 2/2] [WIP] Allow running git init on a remote repository specification Peter Krefting
2010-11-13 21:29 ` Sverre Rabbelier
2010-11-16 5:33 ` Peter Krefting
2010-11-16 17:58 ` Junio C Hamano
2010-11-16 20:12 ` Peter Krefting
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=cover.1289561504.git.peter@softwolves.pp.se \
--to=peter@softwolves.pp.se \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.