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.

Sign up for GitHub

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

Jump to bottom

doc: update branch to master #1511

Closed
wants to merge 1 commit into from
Closed

doc: update branch to master #1511

wants to merge 1 commit into from

Conversation

silverwind
Copy link
Contributor

Updated the markdown files to refer our new main branch.

@silverwind silverwind added the doc Issues and PRs related to the documentations. label Apr 23, 2015
@Fishrock123
Copy link
Member

LGTM, can you check the GOVERNANCE and such files also?

@silverwind
Copy link
Contributor Author

Here's the remaining output of ag -i 'v1\.x', looks fine to me:

CHANGELOG.md
677:* **libuv**: Upgrade to 1.4.2. See [libuv ChangeLog](https://github.com/libuv/libuv/blob/v1.x/ChangeLog) for details of fixes.
824:* **libuv** upgrade to 1.4.0, see [libuv ChangeLog](https://github.com/libuv/libuv/blob/v1.x/ChangeLog)

deps/npm/test/tap/publish-invalid-semver-tag.js
53:  npm.config.set('tag', 'v1.x')
56:    t.same(err.message, 'Tag name must not be a valid SemVer range: v1.x')

deps/openssl/openssl/crypto/camellia/asm/cmll-x86.pl
171:# V1.x API
346:# V1.x API

deps/openssl/openssl/crypto/camellia/asm/cmll-x86_64.pl
116:# V1.x API
226:# V1.x API

deps/uv/CONTRIBUTING.md
40:$ git checkout -b my-feature-branch -t origin/v1.x
43:(Where v1.x is the latest stable branch as of this writing.)
134:$ git rebase upstream/v1.x  # or upstream/master

doc/tc-meetings/2014-12-30.md
81:Action: **Rename to "v1.x", Ben agreed to make the change**

doc/tc-meetings/2015-01-07.md
40:* chris: streams - solving failure on v1.x branch for npm, zlib patch breaks stuff, streams visualization stuff doc/writeup of node streams and whatWG streams

doc/tc-meetings/2015-01-28.md
89:* Chris: branches will be “master” - development happens here, maintain “v1.x”, “v2.x” etc. for major releases. Ideally LTS would be from major versions.

@Fishrock123
Copy link
Member

👍

silverwind added a commit that referenced this pull request Apr 23, 2015
@silverwind
doc: update branch to master
bb254b5 
Update the remaining markdown files to refer to the master branch.
PR-URL: #1511
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
@silverwind
Copy link
Contributor Author

Landed in bb254b5

@silverwind silverwind closed this Apr 23, 2015
@rvagg rvagg mentioned this pull request Apr 27, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
doc Issues and PRs related to the documentations.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@silverwind @Fishrock123