From: walt <wa1ter@myrealbox.com>
To: git@vger.kernel.org
Subject: Re: New behavior for git-branch?
Date: Sun, 03 Feb 2008 06:42:27 -0800 [thread overview]
Message-ID: <fo4jr4$7c0$1@ger.gmane.org> (raw)
In-Reply-To: <fo27d0$gs7$1@ger.gmane.org>
walt wrote:
> ...
> $git-branch -av
> * master ae9458d Merge git://git.infradead.org/battery-2.6
> origin 8af03e7 Merge branch 'for-2.6.25' of
> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc
> origin/master aa62999 x86: fix bootup crash in native_read_tsc()
>
> In my confusion yesterday, I think I created a new 'origin' which
> has nothing to do with Linus' repository -- but I'm not sure...
I fixed it by copying these new settings from Junio's config:
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
branch.master.remote=origin
branch.master.merge=refs/heads/master
prev parent reply other threads:[~2008-02-03 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 16:57 New behavior for git-branch? walt
2008-02-03 14:42 ` walt [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='fo4jr4$7c0$1@ger.gmane.org' \
--to=wa1ter@myrealbox.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;
as well as URLs for NNTP newsgroup(s).