Re: preparing the repository move to gitlab

On 21.04.18 06:46, Don Cohen wrote:
>   ht pull -u

The normal thing would be git fetch + git merge or git pull to update, but:
- the repository at https://gitlab.com/gnu-clisp/clisp is still empty 
(at least for me)
- https://gitlab.com/gnu-clisp/clisp is not defined as a remote after 
executing the instructions

I don't understand what Bruno proposes at all, must be missing an 
important piece.

In my - probably simplistic view - the first steps would have been git 
clone https://gitlab.com/gnu-clisp/clisp.git, but since the repository 
is empty.

Puzzled

Karsten


PS:
git fetch
->
fatal: No remote repository specified.  Please, specify either a URL or 
a remote name from which new revisions should be fetched.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel