From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Stupid Git question
Date: Tue, 21 Nov 2006 22:49:21 +0100 [thread overview]
Message-ID: <ejvs65$vo8$1@sea.gmane.org> (raw)
In-Reply-To: 89b129c60611211341j71079633g53b0ec1d2e3193a5@mail.gmail.com
Sean Kelley wrote:
> git checkout origin
It should be "git checkout master". You shouldn't do work on tracking
branches like origin branch.
> git pull . fm-modulator
>
> git push origin
Here origin means origin remote (repository). Check out what you have in
remotes/origin, or in [remote "origin"] section in git config.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-11-21 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <89b129c60611211331r3bb286b6re3c2c8f65ec3896f@mail.gmail.com>
2006-11-21 21:41 ` Stupid Git question Sean Kelley
2006-11-21 21:49 ` Jakub Narebski [this message]
2006-11-22 14:28 ` Sean Kelley
2006-11-22 16:44 ` Carl Worth
2006-11-22 21:28 ` Sean Kelley
2006-11-22 22:43 ` Junio C Hamano
2006-11-24 8:31 ` Junio C Hamano
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='ejvs65$vo8$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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