From: Jon Loeliger <jdl@freescale.com>
To: Anatoly Yakovenko <aeyakovenko@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Mike Hommey <mh@glandium.org>,
git@vger.kernel.org
Subject: Re: cant get git to work over http
Date: Tue, 19 Feb 2008 12:24:00 -0600 [thread overview]
Message-ID: <47BB1EC0.601@freescale.com> (raw)
In-Reply-To: <e26d18e40802191019j48a1ceadk4887ffc35100ab0a@mail.gmail.com>
Anatoly Yakovenko wrote:
>>> $ git-pull
>>> fatal: 'origin': unable to chdir or not a git archive
>>> fatal: The remote end hung up unexpectedly
>> Since you did not clone from anywhere, the remote "origin" is not set.
>> You will have to do that yourself:
>>
>> git remote add -f origin http://aeyakovenko@myserver.com/git/repo/
>
> Thanks, that worked. but push still gives me an error:
>
> $ git pull
> 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
> name which branch you want to merge on the command line and
> try again (e.g. 'git pull <repository> <refspec>').
> See git-pull(1) for details on the refspec.
>
> If you often merge with the same branch, you may want to
> configure the following variables in your configuration
> file:
>
> branch.master.remote = <nickname>
> branch.master.merge = <remote-ref>
> remote.<nickname>.url = <url>
> remote.<nickname>.fetch = <refspec>
>
> See git-config(1) for details
Did you follow this advice? You've set up the
origin's URL now, and so it knows from where the
fetch step will happen, but have you set up the
merge step yet? Does it know what branches to
merge on that pull request?
jdl
next prev parent reply other threads:[~2008-02-19 18:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 0:49 cant get git to work over http Anatoly Yakovenko
2008-02-19 6:39 ` Mike Hommey
2008-02-19 7:09 ` Anatoly Yakovenko
2008-02-19 9:39 ` Mike Hommey
2008-02-19 11:18 ` Johannes Schindelin
2008-02-19 18:19 ` Anatoly Yakovenko
2008-02-19 18:24 ` Jon Loeliger [this message]
2008-02-19 19:06 ` Anatoly Yakovenko
2008-02-19 19:19 ` Johannes Schindelin
2008-02-19 19:27 ` Anatoly Yakovenko
2008-02-19 19:41 ` Johannes Schindelin
2008-02-19 19:53 ` Anatoly Yakovenko
2008-02-19 19:57 ` Johannes Schindelin
2008-02-19 19:57 ` Jeff King
2008-02-19 20:05 ` Jon Loeliger
2008-02-19 21:05 ` Anatoly Yakovenko
2008-02-19 21:55 ` Jon Loeliger
2008-02-19 21:59 ` Anatoly Yakovenko
2008-02-19 22:13 ` Anatoly Yakovenko
2008-02-19 22:20 ` Johannes Schindelin
2008-02-20 13:46 ` Anton Gladkov
2008-02-20 10:39 ` Robert Haines
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=47BB1EC0.601@freescale.com \
--to=jdl@freescale.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=aeyakovenko@gmail.com \
--cc=git@vger.kernel.org \
--cc=mh@glandium.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 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).