From: Ian Kent <raven@themaw.net>
To: autofs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] autofs 5.1.0 release
Date: Thu, 05 Jun 2014 13:45:23 +0800 [thread overview]
Message-ID: <1401947123.2560.19.camel@perseus.fritz.box> (raw)
[-- Attachment #1: Type: text/plain, Size: 1762 bytes --]
Hi all,
A lot of testing has been done to check that the amd format map
implementation doesn't break existing function. There's more to
do but it's time to release 5.1.0.
autofs
======
The package can be found at:
ftp://ftp.kernel.org/pub/linux/daemons/autofs/v5
It is autofs-5.1.0.tar.[gz|xz]
No source rpm is there as it can be produced by using:
rpmbuild -ts autofs-5.1.0.tar.gz
and the binary rpm by using:
rpmbuild -tb autofs-5.1.0.tar.gz
See the README.amd-maps file for information about using amd format
maps.
Here are the entries from the CHANGELOG which outline the updates:
- fix mistake in assignment (included in 5.1.0-beta1).
- add amd map format parser (included in 5.1.0-beta1).
- check for non existent negative entries in lookup_ghost().
- fix reset flex scan buffer on init.
- fix fix negative status being reset on map read.
- amd lookup update lookup ldap to handle amd keys.
- inadvertantly dropped from initial series.
- amd lookup update lookup hesiod to handle amd keys.
- inadvertantly dropped from initial series.
- fix wildcard key lookup.
- fix out of order amd timestamp lookup.
- fix ldap default schema config.
- fix ldap default master map name config.
- fix map format init in lookup_init().
- fix incorrect max key length in defaults get_hash().
- fix xfn sets incorrect lexer state.
- fix old style key lookup.
- fix expire when server not responding.
- fix ldap_uri config update.
- fix typo in conf_load_autofs_defaults().
- fix hash on confg option add and delete.
- add plus to path match pattern.
- fix multi entry ldap option handling.
- cleanup options in amd_parse.c
- allow empty value for some map options.
- allow empty value in macro selectors.
Ian
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2014-06-05 5:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1401947123.2560.19.camel@perseus.fritz.box \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®