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

Revise file names and dir layout for issue 360 #367

Conversation

pnkfelix
Copy link
Member

@pnkfelix pnkfelix commented Oct 8, 2014

This commit just:

* combines the `complete/` and `active/` directories into one: `text/`

* renames all of the RFC text files to use their earliest associated
  PR number as the RFC number.

A follow-on commit encodes the `active`/`complete` distinction into a
list in the README.md file, and fixes a few mistakes in the RFC files
that I encountered along the way.
In particular:

* The RFC associated with rust-lang#127 should have had a link to rust-lang#19 as well
  (and has been assigned RFC rust-lang#19); it also was revised to match the
  markdown href style of other RFCs.

* RFC rust-lang#34 needed its header entries filled in,

* RFC rust-lang#123 had a typo in its header, and

* RC rust-lang#155 was revised to match the markdown href style of other RFCs.
Added a table-of-contents in the hopes that will ease navigation: the
document now starts off with the active list after the introduction,
so I anticipate that one will not see as much of the expository text
as one used to, and thus the table of contents will help someone who
is skimming to find their objective.
@pnkfelix
Copy link
Member Author

pnkfelix commented Oct 8, 2014

r? any core team member.

The main things I'd like feedback on:

  • Are there any issues with my chosen name text/ for the combined subdir?
  • Does the new README.md seem right?
  • Did I cover everything in my changes to the process document.

@nikomatsakis
Copy link
Contributor

This all seems reasonable to me.

@pnkfelix
Copy link
Member Author

@brson @alexcrichton hey did you want to take a look at this too? Or shall I just merge it? (If possible, I would like to resolve the PR before any other RFC PR's get merged, i.e. before the Tuesday mtg.)

@alexcrichton
Copy link
Member

I was hoping to get some broader discussion on this before merging, and we can always be sure to merge this first before we merge anything else (we merge pretty rarely)

@pnkfelix
Copy link
Member Author

@alexcrichton okay i will put this PR on the mtg agenda then.

brson added a commit that referenced this pull request Oct 14, 2014
…ayout-for-issue-360

Revise file names and dir layout for issue 360
@brson brson merged commit 091e5fa into rust-lang:master Oct 14, 2014
@Centril Centril added the not-rfc For PRs that fix things like spelling mistakes, wrong file names, etc. label Nov 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not-rfc For PRs that fix things like spelling mistakes, wrong file names, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

meta-issue: what href should one use to refer to RFC's?
5 participants