Using Git to update underlying library but keep changes -


i have case history of library upon made work, , of work have diverged. time after branched off of original branch contains library 1.0, library's developer released update, need incorporate end result, keeping changes made on top of that.

there answer similar question here. however, many experienced git users not recommend rebasing commits public, , reason: history re-written. attached previous commits lost. keeping pull requests "book-keeping" become useless. so, what best approach if want achieve similar result, keep history sane, and, more importantly, have local repositories of collaborators consistent?

i expect developer of underlying library make new releases once in while, , process needs repeated every time, drawbacks. graph this:

product ------p1--p2--p3--p4'--p5--p6'              /           /        / library ---l1----------l2-------l3 

anyone?

use git merge instead of git rebase. create "merge commit" rather re-writing history.

for example:

git fetch git merge library/master 

Comments

Popular posts from this blog

toolbar - How to add link to user registration inside toobar in admin joomla 3 custom component -

linux - disk space limitation when creating war file -