You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 28, 2021. It is now read-only.
It's only checking whether the incoming commit is taller than the existing commit. It doesn't check the ancestry at all. So committing x<-y<-z on top of a<-b would succeed. Worse, the ref height takes into account the entire chunk hierarchy including values, not just the commits. So committing something like x on top of a<-b<-c would also work if x contains a chunk hierarchy that is bigger than c's.
It doesn't look like it to me.
It's only checking whether the incoming commit is taller than the existing commit. It doesn't check the ancestry at all. So committing
x<-y<-z
on top ofa<-b
would succeed. Worse, the ref height takes into account the entire chunk hierarchy including values, not just the commits. So committing something likex
on top ofa<-b<-c
would also work if x contains a chunk hierarchy that is bigger thanc
's.https://github.com/attic-labs/noms/blob/master/go/datas/database_common.go#L121
In order to implement fast-forward correctly, we must know all commits refs that are reachable from a given commit.
The text was updated successfully, but these errors were encountered: