Hello,
thank you for this nice and quick fix of this corner case!
Stepan
Jeff King writes:
> Subject: merge-base: handle --fork-point without reflog
>
> The --fork-point option looks in the reflog to try to find
> where a derived branch forked from a base branch. However,
> if the reflog for the base branch is totally empty (as it
> commonly is right
On Wed, Oct 12, 2016 at 12:32:09PM -0400, Jeff King wrote:
> > The problem seems to be that command
> > git merge-base --fork-point refs/remotes/origin/tmp refs/heads/tmp
> > returns nothing, because the refs are packed.
>
> The --fork-point option looks in the reflog to notice that the
On Wed, 13 Apr 2005, Linus Torvalds wrote:
I agree. But I did the silly common revision tracking part slightly
differently and in particular I already made fsck and rev-tree use the
same exact code.
I think I only saw a cut-and-paste version, and I didn't want to follow
that pattern.
Also,
4 matches
Mail list logo