Re: push rejected (non-fast-forward)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thank you Junio.

Do you know how the

    $ git pull origin so-much-foo` 

command manages to keep user-two’s branch up-to-date with remote?

It seems counterintuitive since I am pulling from origin and not explicitly working with remote.
 
Would what you see here been an acceptable scenario?
https://github.com/user-one/project/pull/1

I performed a `git pull` and merged the changes manually. This looks like an awful lot to keep track of, and I’m not sure if it’s acceptable for larger projects.

My goal here is to prepare myself to help out with a large open source project.

Also, if anyone has the patience, would you mind explaining what’s going on here?

$ git show-branch FETCH_HEAD so-much-foo
! [FETCH_HEAD] changed foo/foo.txt contents to "so much foo"
 * [so-much-foo] foo/foo.txt from "so much foo" to "foo\nfoo"
--
 * [so-much-foo] foo/foo.txt from "so much foo" to "foo\nfoo"
 * [so-much-foo^] changed foo/foo.txt contents to "so much foo"
 * [so-much-foo~2] file-two.txt with contents "file two"
+  [FETCH_HEAD] changed foo/foo.txt contents to "so much foo"
+* [so-much-foo~3] foo/ and foo/foo.txt with contents "foo"


Thank you for the help!--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]