From: Seth Falcon <sethfalcon@gmail.com>
To: git@vger.kernel.org
Subject: Re: Confused about tracking git master
Date: Tue, 18 Apr 2006 12:47:18 -0700 [thread overview]
Message-ID: <m2y7y2eke1.fsf@ziti.fhcrc.org> (raw)
In-Reply-To: <20060418185937.GD13672@vsectoor.geht-ab-wie-schnitzel.de> (Nicolas Vilz's message of "Tue, 18 Apr 2006 20:59:37 +0200")
Nicolas Vilz <niv@iaglans.de> writes:
> You are trapped with the pu branch imho, like many others before *G* ...
> simply do a
>
> Pull: +refs/heads/pu:refs/heads/pu
>
> in your .git/remotes/origin file or remove that pu line...
Thank you! That seems to get me going again. But, isn't this going
to trip up other newbies? I just tried a fresh git clone and the pu
branch comes in...
It would improve one's first impressions to not have to edit
.git/remotes/origin (although it is instructional) just to stay up to
date with git.
Cheers,
+ seth
prev parent reply other threads:[~2006-04-18 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 18:08 Confused about tracking git master Seth Falcon
2006-04-18 18:59 ` Nicolas Vilz
2006-04-18 19:47 ` Seth Falcon [this message]
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=m2y7y2eke1.fsf@ziti.fhcrc.org \
--to=sethfalcon@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