Lixia (Sylvia) Lei

## Scenario 2: OCI Layout Suppose there is such a DAG, where manifest A is referenced by manifest B as a layer and is referenced by manifest list C as...

## Scenario 3: Repository Double CASs Suppose the below DAG is being copied to a remote repository, should manifest A be pushed via the manifest endpoint or via the blob...

Interestingly, the [`docker buildx build`](https://docs.docker.com/engine/reference/commandline/buildx_build/) command generates build caches like this: Putting layers in the `manifests` field of an OCI image index. When copying such structure to a remote repository,...

We may need to introduce a new method to return leaf successors and non-leaf successors separately, as a complement to `content.Successors()`. https://github.com/oras-project/oras-go/blob/76382aaa94873ad14fddacdbff0f5ed32f43c3aa/content/graph.go#L47-L106

@dextrot Thanks for the contribution! Could you address the remaining comments and rebase?

> My limited understanding is that graph is used for predecessor/successor (aka parent/child) lookups and traversal of content and is populated in Store.Push where it calls graph.Index and during loadIndex...

> Where is this going. Any progress on the `oci.DeletableStore` ? FYI, here is the PR authored by @wangxiaoxuan273: #614

Hi @lht2017 , thanks for the PR. Before we can review the PR, let's discuss the issue in #750 .

> I saw the behaviour as I'm working on resumable downloads and just removed it. Hi @dtroyer-salad , we have not put efforts on this perf enhancement because we were...

We may want to add a few more examples into https://pkg.go.dev/oras.land/oras-go/[email protected]/content/file#pkg-examples.