I'm using some code for which no SCM is used+ and receive occasional updates in the form of all project files although only some of them have been changed only a bit. Up till now I just put my own changes in a git repo and solved these "updates" with a manual git add -p
session which is getting more and more annoying with the amount of my own changes (those that are not determined to be published yet) increasing, and since luckily I did git commit --author "the others"
for aforementioned "patches", I'd like to know:
How can all commits made by one author be separated into a new branch?
(I don't mind rewriting history in this case, the repo is only used by me)
The ideal solution would include a merge of the others' branch into mine after every "patch", but for now a final merge at the end may suffice.
+ yes, the Jedi did feel you cringe there
I'm not quite understanding what you are doing, but the problem you describe with a third party codebase, is called a "vendor branch". Here is how I would handle it:
Make a branch for the third party version, e.g.
vendor
. I assume your branch is calledmaster
. When they publish a new version, you can do the following:ps. rather than
git add -p
, I'd usegit gui
. I was sceptical of using a gui to begin with, but I couldn't live withoutgit gui
andgitk
now (orgitx
on a mac).I recently did this for someone:
Hope this helps