Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Add JIT Coding Conventions document in markdown format #1004

Merged
merged 1 commit into from
May 19, 2015

Conversation

BruceForstall
Copy link

Please review that I've done the markdown formatting "correctly", not the content of the document.

/cc @richlander @briansull @CarolEidt @sivarv @schellap @cmckinsey

@BruceForstall BruceForstall added the documentation Documentation bug or enhancement, does not impact product or test code label May 16, 2015
@CarolEidt
Copy link

LGTM

@ellismg
Copy link

ellismg commented May 19, 2015

Bugs me a little bit that the TOC starts numbering at 4, but I sort of understand why that happened.

@ThomsonTan
Copy link

I am wondering why the "Contents" section starts from # 4.

@BruceForstall
Copy link
Author

Regarding TOC starting at section 4: that's a remnant of the conversion from Word. Unfortunately, markdown format is, uh, simple, so renumbering everything would be a huge pain. Maybe there's a tool that can do this easily (that I don't know about). Anyway, IMO, not a big deal. If we ever want to add sections and need to renumber, then it will become annoying and problematic.

@BruceForstall BruceForstall force-pushed the JitCodingConventions branch from 2035189 to 0d8da10 Compare May 19, 2015 23:15
@BruceForstall
Copy link
Author

I responded to feedback and squashed the commits.

CarolEidt added a commit that referenced this pull request May 19, 2015
Add JIT Coding Conventions document in markdown format
@CarolEidt CarolEidt merged commit b03af64 into dotnet:master May 19, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Documentation bug or enhancement, does not impact product or test code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants