Russ Cox

Updated the top comment to match the new QUICResumeSession.

This proposal has been added to the [active column](https://go.dev/s/proposal-status#active) of the proposals project and will now be reviewed at the weekly proposal review meetings. — rsc for the proposal review...

@neild is the top comment still an accurate definition of the proposal?

Based on the discussion above, this proposal seems like a **[likely accept](https://go.dev/s/proposal-status#likely-accept)**. — rsc for the proposal review group Proposal is in top comment: https://github.com/golang/go/issues/63691#issue-1957426600

No change in consensus, so **[accepted](https://go.dev/s/proposal-status#accepted)**. 🎉 This issue now tracks the work of implementing the proposal. — rsc for the proposal review group Proposal is in top comment: https://github.com/golang/go/issues/63691#issue-1957426600

This proposal has been added to the [active column](https://go.dev/s/proposal-status#active) of the proposals project and will now be reviewed at the weekly proposal review meetings. — rsc for the proposal review...

What if we add a new MajorUpdate field to the Module struct that is output from go list -m, with these semantics: - go list -m -u # sets Deprecated,...

Have all remaining concerns about this proposal been addressed? The proposal details are in https://github.com/golang/go/issues/67420#issuecomment-2150584249.

No, each -u contains one result, since the (pre-existing) Update field can only describe one version.

Based on the discussion above, this proposal seems like a **[likely accept](https://go.dev/s/proposal-status#likely-accept)**. — rsc for the proposal review group The proposal details are in https://github.com/golang/go/issues/67420#issuecomment-2150584249.