Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the result publishable. #11

Closed
wants to merge 1 commit into from
Closed

Conversation

cabo
Copy link
Contributor

@cabo cabo commented Jul 22, 2024

This makes IETF -03 publishable.
However, this breaks the CI.
The renaming has to be completed.
But where is the repo from which IETF -02 was submitted?

@thomas-fossati
Copy link
Collaborator

[...] The renaming has to be completed.

not sure I understand. Does that mean this PR should also include a:

git mv draft-birkholz-cose-tsa-tst-header-parameter.md draft-ietf-cose-tsa-tst-header-parameter.md

?

But where is the repo from which IETF -02 was submitted?

IIRC, for -02 I did a manual submission.

@cabo
Copy link
Contributor Author

cabo commented Jul 22, 2024

[...] The renaming has to be completed.

not sure I understand. Does that mean this PR should also include a:

git mv draft-birkholz-cose-tsa-tst-header-parameter.md draft-ietf-cose-tsa-tst-header-parameter.md

Yes, and some diddling with i-d-template, which has to learn about this change, too.

But where is the repo from which IETF -02 was submitted?

IIRC, for -02 I did a manual submission.

So you took the .md from here and changed draft-birkholz into draft-ietf in there before kdrfc'ing manually?

(Which is what I did for -03 on Henk's request; one of the authors needs to accept that submission.)

@henkbirkholz
Copy link
Member

This takes a few more steps. We'll probably butcher that into main (when Thomas is distracted...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants