Re: Now what: multiple HEAD refs

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: Now what: multiple HEAD refs

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

Alex Riesen [off-list ref] writes:
just a heads-up for everyone tried "git pull" after using "git merge" too much:

$ git pull . ref1 HEAD (notice the space!)
If you were too used to git merge, you would have wrote
HEAD before ref1, so that does not sound plausible ;-).

        $ git pull . maint HEAD
        error: no such remote ref refs/heads/HEAD
        Fetch failure: .
	$ echo $?
        1

But worse yet, the above syntax is to create an Octopus, and you
probably did not mean that.

I think the reason why my trial here worked correctly while you
had trouble with it is because I have the send-pack fix from
Pasky last night.

Re: Now what: multiple HEAD refs

From: Alex Riesen <hidden>
Date: 2016-06-15 22:42:15

On 12/15/05, Junio C Hamano [off-list ref] wrote:
quoted
just a heads-up for everyone tried "git pull" after using "git merge" too much:

$ git pull . ref1 HEAD (notice the space!)
If you were too used to git merge, you would have wrote
HEAD before ref1, so that does not sound plausible ;-).
no, that I have remembered. What I constantly forget is the
space-vs-colon difference.
        $ git pull . maint HEAD
        error: no such remote ref refs/heads/HEAD
        Fetch failure: .
        $ echo $?
        1

But worse yet, the above syntax is to create an Octopus, and you
probably did not mean that.
no, of course not.
I think the reason why my trial here worked correctly while you
had trouble with it is because I have the send-pack fix from
Pasky last night.
yes, probably. It cleanups a reference if there was an error, right?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help