Neil Williams 90cfcaaecc Update license headers to 2014. ...

Ok, now I'm getting some angst in my commit messages like my
predecessors had.  I understand now.  It's a terrible burden.  Why must
the calendar progress?  Why must numbers increment?  The world is
forever turning.

The future is here.

It is 2014.

2014-05-02 16:26:31 -04:00

..

migrate

Update license headers to 2014.

2014-05-02 16:26:31 -04:00

traffic

Update license headers to 2014.

2014-05-02 16:26:31 -04:00

clean_static_files.py

Update license headers to 2014.

2014-05-02 16:26:31 -04:00

compute_time_listings

compute_time_listings MINID query: order by date

2014-02-26 11:44:08 -08:00

log_q.py

Update license headers to 2014.

2014-05-02 16:26:31 -04:00

manage-consumers

manage-consumers: Allow for subtyped consumers.

2013-06-19 16:12:24 -07:00

promoted_links.py

Update license headers to 2014.

2014-05-02 16:26:31 -04:00

read_secrets

Update license headers to 2014.

2014-05-02 16:26:31 -04:00

saferun.sh

Update license headers to 2014.

2014-05-02 16:26:31 -04:00

tracker.py

Update license headers to 2014.

2014-05-02 16:26:31 -04:00

trylater.py

Automatically delete password hashes of deleted accounts.

2014-02-26 12:45:55 -08:00

upload_static_files_to_s3.py

Update license headers to 2014.

2014-05-02 16:26:31 -04:00

wrap-job

wrap-job: Don't cd into r2/r2/ when we just want to be in r2/.

2013-02-14 14:18:47 -08:00

write_live_config

Update license headers to 2014.

2014-05-02 16:26:31 -04:00

write_secrets

Update license headers to 2014.

2014-05-02 16:26:31 -04:00