Re: How to make "git push/pull" work in non-clone repo?

Thank for your hints. I get "git push" work. The "git pull" need argument.

/d/workspace/git
$ ls
depot  work1  work2

/d/workspace/git
$ git clone --bare work1 depot
Cloning into bare repository depot...
done.

/d/workspace/git/work1 (master)
$ git push
fatal: No destination configured to push to.

/d/workspace/git/work1 (master)
$ git pull
fatal: No remote repository specified.  Please, specify either a URL or a
remote name from which new revisions should be fetched.

/d/workspace/git/work1 (master)
$ git remote add origin ../depot

/d/workspace/git/work1 (master)
$ git push
Everything up-to-date

/d/workspace/git/work1 (master)
$ git pull
From ../depot
 * [new branch]      master     -> origin/master
You asked me to pull without telling me which branch you
want to merge with, and 'branch.master.merge' in
your configuration file does not tell me, either. Please
specify which branch you want to use on the command line and
try again (e.g. 'git pull <repository> <refspec>').
See git-pull(1) for details.

If you often merge with the same branch, you may want to
use something like the following in your configuration file:

    [branch "master"]
    remote = <nickname>
    merge = <remote-ref>

    [remote "<nickname>"]
    url = <url>
    fetch = <refspec>

/d/workspace/git/work1 (master)
$ git pull origin master:master
Already up-to-date.
2011/11/4 Kirill Likhodedov [off-list ref]:

03.11.2011, в 17:59, Hong-Ming Su:

quoted

I create a repo X with git init. After several commit in X, I clone a
bare repo Y from X.
I try to continue work in X, and push to/pull from Y. The command git
push and git pull fails. I see the error message but I do not know
which git command can fix that problem.
Then I clone Z from Y. git push/pull works in Z.
How to make "git push/pull" the same in X as in Z?

By cloning Y from X you made X to be a parent of Y while you need vice versa.
To fix this add Y as a remote to X and set up tracking for you master branch.

By the way, in such cases you'd better write commands you've executed, and the error report you've got.
" I see the error message but I do not know which git command can fix that problem" - this is zero of useful information.

----------------------------------
Kirill Likhodedov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"