> Thank you for the answer, but it's not what I want )) > Applying patches is the same as rebasing, I guess. > But I do not want to change v2.5-repo (let's call it so) that much. > I'd like to know is there any method (low-level I suppose, as far as Git > manages tree-objects as files) to make v2.4 LAST commit to be the > parent of v2.5 FIRST commit? > This is impossible. The commit-id is calculated from the history of the whole repository. So you must rebase in the sense of dependency on another history. My method enables to rebase on the same content of the repository. -- 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