Junio C Hamano <gitster@xxxxxxxxx> writes:
> ... As announced, I'll rewind
> and rebuild "next" with the surviving topics on top of "master",
> sometime tomorrow.
... which just happened. The old history leading to "next" used
to be 1323 commits ahead of v1.5.4.2 but the rebased one now is
only 182 commits ahead, mostly due to old merge commits that
never went out of "next" to "master" and a handful reverts.
On k.org and repo.or.cz repo, I pushed out a branch "old-next"
whose ancestry is connected to the old "next" and whose tip-tree
matches that of the tip of "next", so if any of you have been
building on top of 'next', you may want a one-time conversion to
do:
$ git fetch
$ git rebase --onto origin/next origin/old-next my-branch-on-next
Recent "git pull --rebase" may be good enough by consulting
your remotes/origin/next@{1} to find the base without using the
old-next trick, though I haven't checked.
-
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
