News for hackers. Stuff that matters.

A comment on Mercurial RFC of a new extension to directly operate on Git repositories. Parent comment

Re:Mercurial RFC of a new extension to directly operate on G... by mehrdadn on Wednesday October 30, 2019 @04:34AM (#21395600)
> Your view on commit is a logical set of changes. Git's view is state of the repository.

No, my view of a commit is not a logical set of changes. It's everything that would be in my worktree if I checked out the commit. Which is neither merely the changes from the previous commit(s), nor the entire history leading to the current commit.

[ Parent | on HN ]
Re:Mercurial RFC of a new extension to directly operate on G... by karatinversion on Wednesday October 30, 2019 @05:07AM (#21395767)
But git already has this object, it’s called a tree and each commit has a unique tree associated with it. The commits are the object that carries history and metadata on top of the trees. Is your objection that the commit metadata is associated to the commit and not the tree?
[ Parent | on HN ]
Re:Mercurial RFC of a new extension to directly operate on G... by mehrdadn on Wednesday October 30, 2019 @05:13AM (#21395785)
To a first approximation, yes, I think that captures the general idea.

But I don't think it's literally as simple as just taking the commit metadata and slapping it onto the tree objects.

[ Parent | on HN ]