linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brandon Philips <brandon@ifup.org>
To: acl-devel@nongnu.org
Cc: linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com
Subject: [ANNOUNCE] acl: 2.2.50 release
Date: Mon, 18 Apr 2011 11:59:46 -0700	[thread overview]
Message-ID: <20110418185946.GC335@Maya.local> (raw)

Hello-

acl 2.2.50 is released. You can find it here:
 http://download.savannah.gnu.org/releases/acl/acl-2.2.50.src.tar.gz

The git repo is here and the tag is v2.2.50:
 http://git.savannah.gnu.org/cgit/acl.git/

Here comes the shortlog:

Andreas Gruenbacher (4):
      setfacl: Clarify that removing a non-existent acl entry is not an error
      Fix a typo in the setfacl man page
      OPTIONS in man pages should be a section heading, not a subsection heading
      Minor fixes to the previous commit

Brandon Philips (5):
      setfacl: changing owner and when S_ISUID should be set --restore fix
      setfacl: print useful error from read_acl_comments
      libacl: fix potential null pointer dereference
      libacl/Makefile: add __acl_extended_file.h to HFILES
      VERSION: v2.2.49 -> v2.2.50

Kamil Dudka (2):
      Prevent setfacl --restore from SIGSEGV on malformed restore file
      libacl: Add acl_extended_file_nofollow()

M. Steinborn (1):
      setfacl: make sure that -R only calls stat(2) on symlinks when it needs to

Markus Steinborn (1):
      setfacl: fix restore crash on malformed input

Mike Frysinger (1):
      improve AC_PATH_PROG usage

Cheers,

	Brandon

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

                 reply	other threads:[~2011-04-18 18:59 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=20110418185946.GC335@Maya.local \
    --to=brandon@ifup.org \
    --cc=acl-devel@nongnu.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=xfs@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).