Vincent van Ravesteijn <v...@lyx.org> writes:
>> | This worked seemingly perfekt (except for the strangish history) for
>> | 1.5.3.
>>
>> grafts does not get resolved by a clone. Seems that git-filter-branch is
>> required for that.
>
| I don't really understand the problem. In the git repo it's pretty
| easy to split commits and rewrite the history right ?
It is easy enought to split a commit, but then history from there to
present will be rewritten. No commit ids will be the same f.ex. This
makes git svn fail. (And I am using git svn to have a countinously
updated tree).
| What do you mean by "grafting" ? What steps do you try to do ?
gitglossary - grafts:
Grafts enables two otherwise different lines of development to be
joined together by recording fake ancestry information for commits.
This way you can make git pretend the set of parents a commit has
is different from what was recorded when the commit was created.
Configured via the .git/info/grafts file.
I use this to make the tag be on the correct branch, and not on a "svn
tag branch".
--
Lgb
