Re: Short rant about git usability - make 'git clone' work on an empty remote repository

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Heya,

On Thu, Jan 22, 2009 at 11:02, Richard W.M. Jones <rjones@xxxxxxxxxx> wrote:
>  $ git clone git+ssh://rwmj@xxxxxxxxxxxxxxxxx/gitroot/ocaml-autoconf/ocaml-autoconf.git
>  Initialized empty Git repository in /home/rjones/d/ocaml-autoconf/.git/
>  fatal: no matching remote head
>  $ mkdir ocaml-autoconf
>  $ cd ocaml-autoconf
>  $ git init
>  Initialized empty Git repository in /home/rjones/d/ocaml-autoconf/.git/
>  $ git remote add origin git+ssh://rwmj@xxxxxxxxxxxxxxxxx/gitroot/ocaml-autoconf/ocaml-autoconf.git
>  $ echo test > README
>  $ git add README
>  $ git commit
>  Created initial commit 2c9a63a: Create repository.
>   1 files changed, 1 insertions(+), 0 deletions(-)
>   create mode 100644 README
>  $ git push origin master

Is, as far as I can see, the minimal you could have done to get your
remote set up. You are right in that cloning an empty repository would
be nice to have as it would save having to remember to do about 8
different commands. Then again, after digging through the source for
half an hour I'm still not sure I even understand what's going on, let
alone know how to fix it ;). You should ask on #git for cloning empty
dir support, maybe it'll annoy Dscho enough to fix it.


-- 
Cheers,

Sverre Rabbelier
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux