thought on reversing commits to adjusted branch
This commit is contained in:
parent
f49570857c
commit
5716c39928
1 changed files with 6 additions and 0 deletions
|
@ -209,6 +209,12 @@ which to not delete when reversing it?
|
||||||
So, a reverse filter may need some state that was collected when running
|
So, a reverse filter may need some state that was collected when running
|
||||||
the filter forwards, in order to decide what to do.
|
the filter forwards, in order to decide what to do.
|
||||||
|
|
||||||
|
Alternatively, instead of reverse filtering the whole adjusted tree,
|
||||||
|
look at just the new commit that's being propigated back from the
|
||||||
|
adjusted to master branch. Get the diff from it to the previous
|
||||||
|
commit; the changes that were made. Then de-adjust those changes,
|
||||||
|
and apply the changes to the master branch.
|
||||||
|
|
||||||
## push
|
## push
|
||||||
|
|
||||||
The new master branch can then be pushed out to remotes. The
|
The new master branch can then be pushed out to remotes. The
|
||||||
|
|
Loading…
Reference in a new issue