Difference between revisions of "How to do git tricks"
Line 14: | Line 14: | ||
https://stackoverflow.com/questions/2364147/how-to-get-just-one-file-from-another-branch | https://stackoverflow.com/questions/2364147/how-to-get-just-one-file-from-another-branch | ||
− | ==Cherry pick | + | ==Cherry pick== |
− | + | Sometimes git cherry-pick will work across files having different paths and sometimes just creates new paths, which is not helpful. Not sure why. The same cherry-pick on different computers will do different things. | |
− | + | ||
+ | Be sure to do | ||
+ | <pre> | ||
+ | git diff HEAD^ | ||
+ | </pre> | ||
+ | to be sure what changes are being made and to minimize them. | ||
==Patch== | ==Patch== |
Revision as of 07:20, 21 January 2019
Find last commit where line existed
blame --reverse START
Comparing files
git diff branch1:full/path/to/foo.txt branch2:full/path/to/foo-another.txt
How to link to such comparison view on github?
Compare and copy files from other branches
https://stackoverflow.com/questions/2364147/how-to-get-just-one-file-from-another-branch
Cherry pick
Sometimes git cherry-pick will work across files having different paths and sometimes just creates new paths, which is not helpful. Not sure why. The same cherry-pick on different computers will do different things.
Be sure to do
git diff HEAD^
to be sure what changes are being made and to minimize them.
Patch
git log -p -1 <sha1-of-your-commit>
https://stackoverflow.com/questions/7802252/why-cherry-pick-pick-change-more-than-one-commit
"Git goes back in the history until the cherry pick source matches the target and creates the patch based on this revision. That's why more changes might appear ..."
git log -p -1 <sha1> | git apply --3way -
But this pulls more changes too. And without --3way fails.
To modify only one file, see https://www.codefull.org/2018/11/specify-target-file-in-git-cherry-pick/
- Create a patch file for that individual file:
git show [commit hash] -- path/to/old/file > patchfile
- Manually edit the newly created patchfile and replace all occurrences of the old path with the new path.
- Apply the patch via
git apply --3way patchfile
git remote add rep2-git url_to_unrelated_repository git fetch rep2-git git checkout remotes/rep2-git/branch2 git checkout -b rep2/branch2 git push -u origin rep2/branch2:rep2/branch2
There is no need for the two repositories to have a common initial commit or anything. The commit hashes are preserved. You can even git cherry-pick commit from the other repostory and git will do pretty good job finding files to apply the commits to, even if the files have somewhat different names and are in somewhat different locations in the file two file trees.