update postfix queue example
Created symlink for /var/lib/logstash/logstash.jar

The puppet manifests expect it here. If you'd prefer that, i could also change it in the puppet manifests.
add sort filter
Add IPv6 grok pattern.

Rename IP pattern to IPV4 and add new IP pattern that matches either IPV6 or
IPV4 patterns.

IPV6 regex swiped from http://forums.intermapper.com/viewtopic.php?t=452
- swear less, and never in documentation.
- fix docs
- strings are now assumed to always be Unicode
This fixes a bug where this caused a crash:

LANG=C bin/logstash agent -e 'filter { mutate { replace => { "message"
=> "☹" } } } output { stdout { codec => json } }'

The problem was that LANG=C told ruby's eval() what the encoding of
strings was by default, and since logstash requires UTF-8/unicode
elswhere, it makes sense to require it for the config file as well.
filters: date: add target option

Update the date filter to support a target option.  If defined,
instead of updating the @timestamp field, update the given target field.
This is useful for events that have multiple timestamps (e.g., start and
end times).
outputs/riemann: make event tagging work again

As tags on outputs are now deprecated, we pass the tags set at input or
filter stage to Riemann events.

For the record, the idea is to pass along Logstash's events tags to the
Riemann events created, so that filtering *in Riemann* can be done based
on the tags set by Logstash.
outputs/riemann: minor cleanups

 - remove trailing whitespace
 - clarify how tags work + other small documentation updates
Restore class method from_json, as event is no more an included class
Repair outputs/file test + add use of zcat command to cover LOGSTASH-997
.
Fixing S3 input and output

- Input: Fixing inclusion of library ( LOGSTASH-1321 )
- Input: adding better validation for region
- Output: Fixing region validation ( LOGSTASH-1319 )
- don't store geoip data that is nil or empty strings
- update change for geoip fix
Merge pull request #636 from electrical/fix_s3

Fixing S3 input and output
Add option to specify canned ACL in AWS S3 output configuration

    * Adds the option "canned_acl" which defaults to "private"
    * Breaks the previous behaviour where the canned ACL was hard-coded to "public_read".
      Which is a potential security problem, allowing everyone to access the file on S3.
- fix log4j input variable name bug (#635, etc)
- some style fixes
- time must be in UTC (LOGSTASH-1295)