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

"somebody remind me to update this date every year so the docs appear current" #660

Closed
cmawhorter opened this issue Feb 8, 2013 · 3 comments

Comments

@cmawhorter
Copy link

docs/api_template.md

Consider yourself reminded and happy new year ;]

And may I suggest changing this to be 20xx, so that you never have to do this again?

@ctalkington
Copy link
Member

wiki is used now. will be a non-issue once v0.4 out the door as anyone can edit.

@shama
Copy link
Member

shama commented Feb 8, 2013

Funny enough, somebody did that on the wiki near midnight on new years, heh. Here is the commit.

@cmawhorter
Copy link
Author

I don't have that kind of initiative... I'll just create the issue =p

@cowboy cowboy closed this as completed in 25728e1 Mar 12, 2013
jrolfs added a commit to jrolfs/grunt that referenced this issue Mar 16, 2013
* master:
  quote version number for travis
  add node 0.10 to travis
  Bumping version to 0.4.1 and publishing to npm.
  Fix path.join thrown errors with expandMapping rename. Closes gruntjsgh-725.
  Update copyright date to 2013. Closes gruntjsgh-660.
  Remove some side effects from manually requiring Grunt. Closes gruntjsgh-605.
  grunt.log: add formatting support and implicitly cast msg to a string. Closes gruntjsgh-703.
  Update js-yaml to version 2. Closes gruntjsgh-683.
  The grunt.util.spawn method now falls back to stdout when the `grunt` option is set. Closes gruntjsgh-691.
  Making --verbose "Files:" warnings less scary. Closes gruntjsgh-657.
  Fixing typo: the grunt.fatal method now defaults to FATAL_ERROR. Closes gruntjsgh-656, gruntjsgh-707.
  Removed a duplicate line. Closes gruntjsgh-702.
  Gruntfile name should no longer be case sensitive. Closes gruntjsgh-685.
  The grunt.file.delete method warns and returns false if file doesn't exist. Closes gruntjsgh-635, gruntjsgh-714.
  The grunt.package property is now resolved via require(). Closes gruntjsgh-704.
  The grunt.util.spawn method no longer breaks on multibyte stdio. Closes gruntjsgh-710.
  Fix "path.join arguments must be strings" error in file.expand/recurse when options.cwd is not set. Closes gruntjsgh-722.
  Adding a fairly relevant keyword to package.json.
  Bumping version for development.
theasta added a commit to theasta/grunt that referenced this issue Apr 20, 2013
* upstream/master: (21 commits)
  Add grunt logo to readme
  npmignore unneeded files
  quote version number for travis
  add node 0.10 to travis
  Bumping version to 0.4.1 and publishing to npm.
  Fix path.join thrown errors with expandMapping rename. Closes gruntjsgh-725.
  Update copyright date to 2013. Closes gruntjsgh-660.
  Remove some side effects from manually requiring Grunt. Closes gruntjsgh-605.
  grunt.log: add formatting support and implicitly cast msg to a string. Closes gruntjsgh-703.
  Update js-yaml to version 2. Closes gruntjsgh-683.
  The grunt.util.spawn method now falls back to stdout when the `grunt` option is set. Closes gruntjsgh-691.
  Making --verbose "Files:" warnings less scary. Closes gruntjsgh-657.
  Fixing typo: the grunt.fatal method now defaults to FATAL_ERROR. Closes gruntjsgh-656, gruntjsgh-707.
  Removed a duplicate line. Closes gruntjsgh-702.
  Gruntfile name should no longer be case sensitive. Closes gruntjsgh-685.
  The grunt.file.delete method warns and returns false if file doesn't exist. Closes gruntjsgh-635, gruntjsgh-714.
  The grunt.package property is now resolved via require(). Closes gruntjsgh-704.
  The grunt.util.spawn method no longer breaks on multibyte stdio. Closes gruntjsgh-710.
  Fix "path.join arguments must be strings" error in file.expand/recurse when options.cwd is not set. Closes gruntjsgh-722.
  Adding a fairly relevant keyword to package.json.
  ...
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

No branches or pull requests

4 participants