Thread (5 messages) flat view 5 messages, 2 authors, 2016-06-15

Re: git-rebase skips automatically no more needed commits

From: Martin von Zweigbergk <hidden>
Date: 2016-06-15 22:52:00

On Fri, 9 Sep 2011, Francis Moreau wrote:
On Fri, Sep 9, 2011 at 4:23 AM, Martin von Zweigbergk
[off-list ref] wrote:
quoted
you are right that
"git rebase --onto master foo~10 foo" could potentially filter out
patches already in foo..master, without calculating patch-ids for all
commits in master..foo for that matter. I think that would make sense
you meant master..foo~10, didn't you ?
Yes. (I actually did mean "all commits in master..foo", but "_any_
commits in master..foo~10" is more clear and exact.)
please let me know when you submitting your work, I'm interested to see it.
Will do. It's not really that much work, but I'm not sure when I will
have time for it. If you or anyone else is interested in doing it, you
are of course welcome.
quoted
necessary, we could have a flag to disable the filtering e.g. when the
user knows that master is part of a completely separate history from
foo.
Can't git figure this out itself ? (I'm not saying the switch is useless)
Yes, but this hypothetical flag would only be to speed things up by
avoid going to the roots to find out that the histories are disjoint.

Martin
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help