Thread (3 messages) flat view 3 messages, 3 authors, 2016-06-15
  • (off-list ancestor, not in this archive)
  • Re: Now What? · Junio C Hamano <hidden> · 2016-06-15
  • Re: Now What? · Josef Weidendorfer <hidden> · 2016-06-15
  • Re: Now What? · Daniel Barkalow <hidden> · 2016-06-15

Re: Now What?

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:10

Daniel Barkalow [off-list ref] writes:
On Thu, 3 Nov 2005, Junio C Hamano wrote:
quoted
"Peter Eriksen" [off-list ref] writes:
quoted
~/git/git-core]cat .git/remotes/origin
URL: git://git.kernel.org/pub/scm/git/git.git
Pull: master:origin

~/git/git-core]git-checkout maint
~/git/git-core]git pull
You are merging my master into your "maint", probably a copy of
my (previous) maint.
I think the situation is that he really wanted to update master, but 
forgot that he was on the maint branch.
I wonder if it would make sense to have something in .git/remotes/
file that says "run merge only when I am on frotz branch", like
this:

        ~/git/git-core]cat .git/remotes/origin
        URL: git://git.kernel.org/pub/scm/git/git.git
        Pull: master:origin
	Fetch-Only-Unless: master

        ~/git/git-core]git-checkout maint
	~/git/git-core]git pull
	warning: not merging because you are not on 'master' branch.

This would make the above "git pull" behave identical to "git
fetch", and the user can then do:

	$ git checkout master
        $ git pull . origin

Useful?  Useless?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help