Extract dates from .yml files

[tarcieri]

Now that ruby-advisory-db has actual dates, we can extract them from the
.yml files instead of trying to screen scrape them.

This includes regenerated versions of all the input markdown with
updated dates in cases where they were wrong.

[mveytsman]

Is your screen scraping code somewhere? I'd like to use it for something else.

On 2013-04-01, at 7:02 PM, Tony Arcieri [email protected] wrote:

Now that ruby-advisory-db has actual dates, we can extract them from the
.yml files instead of trying to screen scrape them.

This includes regenerated versions of all the input markdown with
updated dates in cases where they were wrong.

You can merge this Pull Request by running

git pull https://github.com/tarcieri/rubysec.github.com leverage_improved_yaml
Or view, comment on, or merge it at:

#4

Commit Summary

Extract dates from .yml files
File Changes

M ruby-advisory-db (2)
R source/_posts/2012-09-08-CVE-2012-6134.markdown (4)
R source/_posts/2012-12-06-CVE-2013-0284.markdown (4)
R source/_posts/2013-01-10-CVE-2013-0285.markdown (4)
R source/_posts/2013-02-19-CVE-2013-1756.markdown (2)
M source/_posts/2013-03-19-CVE-2013-1854.markdown (2)
M source/_posts/2013-03-19-CVE-2013-1855.markdown (2)
M source/_posts/2013-03-19-CVE-2013-1856.markdown (2)
M source/_posts/2013-03-19-CVE-2013-1857.markdown (2)
M tasks/sync_advisories.rake (24)
Patch Links:

https://github.com/rubysec/rubysec.github.com/pull/4.patch
https://github.com/rubysec/rubysec.github.com/pull/4.diff

[tarcieri]

@mveytsman no, but you can find it in the diff: https://github.com/rubysec/rubysec.github.com/pull/4/files#L9L22

[mveytsman]

@tarcieri: thanks!