recent_measurements_excluded_few_count is used twice in bandwidth spec

While going over the spec again during review for #30905 (moved) I stumbled over recent_measurements_excluded_few_count being used twice. The second instance should be relay_recent_measurements_excluded_few_count instead.

changed milestone to %Tor: 0.4.4.x-final

added GeorgKopppen202003 component::core tor/tor milestone::Tor: 0.4.4.x-final owner::gk priority::medium resolution::fixed reviewer::juga severity::normal status::closed tor-spec type::defect labels

bug_33759 (gk/torspec@47b495f5) is up for review.

Trac:
Status: new to assigned
Owner: N/A to gk
Reviewer: N/A to juga

Trac:
Status: assigned to needs_review

Trac:
Keywords: N/A deleted, GeorgKopppen202003 added

thanks!, lgtm. Changing component to Tor cause the spec belongs to it.

Trac:
Component: Core Tor/sbws to Core Tor/Tor
Status: needs_review to merge_ready

Hi, this change looks good, but I don't know how to merge it.

Please provide a git repository and branch, or a GitHub pull request.

Trac:
Status: merge_ready to needs_revision

comment:1 has the branch and the repo. Everything in one link: https://gitlab.torproject.org/gk/torspec/-/tree/bug_33759.

Trac:
Status: needs_revision to merge_ready

Thanks!

Sorry for the confusion, I didn't realise our gitlab was hosting git repositories.

For future reference, the git remote URL I used was:

• https://gitlab.torproject.org/gk/torspec.git

Trac:
Status: merge_ready to closed
Milestone: N/A to Tor: 0.4.4.x-final
Resolution: N/A to fixed

(We don't merge using GitLab or GitHub, so we need the git remote URLs.)

closed

moved to tpo/core/tor#33759 (closed)