From: Mikael Magnusson <mikachu@gmail.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: Short rant about git usability - make 'git clone' work on an empty remote repository
Date: Thu, 22 Jan 2009 12:01:12 +0100 [thread overview]
Message-ID: <237967ef0901220301p47dab7d7hdbf2dccd04a99f16@mail.gmail.com> (raw)
In-Reply-To: <20090122100230.GA9653@amd.home.annexia.org>
2009/1/22 Richard W.M. Jones <rjones@redhat.com>:
> This is a rant, those offended by rants should stop reading now.
>
> When I want to check out a remote repository, I do:
>
> git clone URL...
>
> Except when the repository is empty, when for no explicable reason
> this familiar command doesn't work.
>
> $ git clone git+ssh://rwmj@git.ocamlcore.org/gitroot/ocaml-autoconf/ocaml-autoconf.git
> Initialized empty Git repository in /home/rjones/d/ocaml-autoconf/.git/
> fatal: no matching remote head
>
> $ git init ocaml-autoconf
> usage: git init [-q | --quiet] [--bare] [--template=<template-directory>] [--shared[=<permissions>]]
> $ mkdir ocaml-autoconf
> $ cd ocaml-autoconf
> $ git init
> Initialized empty Git repository in /home/rjones/d/ocaml-autoconf/.git/
> $ ls
> $ ls -a
> . .. .git
>
> Following advice on a website ...
>
> $ git-remote origin git+ssh://rwmj@git.ocamlcore.org/gitroot/ocaml-autoconf/ocaml-autoconf.git
> error: Unknown subcommand: origin
> usage: git remote
> or: git remote add <name> <url>
> or: git remote rm <name>
> or: git remote show <name>
> or: git remote prune <name>
> or: git remote update [group]
>
> -v, --verbose be verbose
>
> $ git remote add origin git+ssh://rwmj@git.ocamlcore.org/gitroot/ocaml-autoconf/ocaml-autoconf.git
>
> $ git status
> # On branch master
> #
> # Initial commit
> #
> nothing to commit (create/copy files and use "git add" to track)
> $ git branch
> $ git checkout
> fatal: You are on a branch yet to be born
> $ git status
> # On branch master
> #
> # Initial commit
> #
> nothing to commit (create/copy files and use "git add" to track)
> $ echo test > README
> $ git commit -a
> # On branch master
> #
> # Initial commit
> #
> # Untracked files:
> # (use "git add <file>..." to include in what will be committed)
> #
> # README
> nothing added to commit but untracked files present (use "git add" to track)
> $ git add README
> $ git commit -a
> Created initial commit 2c9a63a: Create repository.
> 1 files changed, 1 insertions(+), 0 deletions(-)
> create mode 100644 README
>
> $ git push
> No refs in common and none specified; doing nothing.
> Perhaps you should specify a branch such as 'master'.
> fatal: The remote end hung up unexpectedly
> error: failed to push some refs to 'git+ssh://rwmj@git.ocamlcore.org/gitroot/ocaml-autoconf/ocaml-autoconf.git'
> $ git push master
> fatal: 'master': unable to chdir or not a git archive
> fatal: The remote end hung up unexpectedly
> $ git branch master
> fatal: A branch named 'master' already exists.
$ man git-push
$ git push origin master
next prev parent reply other threads:[~2009-01-22 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 10:02 Short rant about git usability - make 'git clone' work on an empty remote repository Richard W.M. Jones
2009-01-22 11:01 ` Mikael Magnusson [this message]
2009-01-22 13:00 ` Sverre Rabbelier
2009-01-22 13:51 ` Johannes Schindelin
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=237967ef0901220301p47dab7d7hdbf2dccd04a99f16@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=git@vger.kernel.org \
--cc=rjones@redhat.com \
/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).