dvcs - git cherry confusion - doesn't work as described in doc -


The article "itemprop =" lesson ">

after

The documentation says:" Because instead of Git-Cherry Committed Id (SHA1), changeset compare, using Git-Cherry To find out whether the local commitments have been implemented under a separate commit id. "

Let's see:

  $ git Cherry Master Release 1.1.0 | Head -1 -1 533e2559342910fbffa2be5b38fdd7f2ddb2ed53 $ git show533e2559342910fbffa2be5b38fdd7f2ddb2ed53 ... (Cherry was 409c61b3304373a73c787fdf9c08cc338934b74d) ...  

The GIT show shows the same changes for 409c .. and 533e

  $ Git br 533e2559342910fbffa2be5b38fdd7f2ddb2ed53 continue -1.1.0 --contains $ Git br --contains 409c61b3304373a73c787fdf9c08cc338934b74d master release -1.0.4  

that means Changeset is both in master and release -1.1.0 then how does git cherry 533e reveal ..?

It also says "Commits are compared to their patch ID, git-patch-id Received from the program. "When your cherry raised diff applied, it is possible to finish being a different diff?

In that case are not only committed a different ID, but also Git- patch-ID as patch report different Patch ID to commit to ID and thus branches to each other

It is easy to check for:.

  Git Show 533e2559342910fbffa2be5b38fdd7f2ddb2ed53 | Git-patch-id git show 409c61b3304373a73c787fdf9c08cc338934b74d | Git- patch-id  

The first SHA1 Git- differ between patch-both runs returned by ID, that is what happened

Warning lector. - I have not tried my theory, but how do I interpret man pages?


Comments

Popular posts from this blog

c++ - Linux and clipboard -

Visual Studio 2005: How to speed up builds when a VSMDI is open? -

booting ubuntu from usb using virtualbox -