public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/elfix:master commit in: /
Date: Sat, 10 Nov 2012 23:38:08 +0000 (UTC)	[thread overview]
Message-ID: <1352590673.83520307969cc118b41f155bed6caebbea87ee6f.blueness@gentoo> (raw)

commit:     83520307969cc118b41f155bed6caebbea87ee6f
Author:     Anthony G. Basile <blueness <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 10 23:37:53 2012 +0000
Commit:     Anthony G. Basile <blueness <AT> gentoo <DOT> org>
CommitDate: Sat Nov 10 23:37:53 2012 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/elfix.git;a=commit;h=83520307

ChangeLog: updated

---
 ChangeLog |   10 ++++++++--
 1 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 0f2533c..5b19976 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,8 +1,14 @@
 2012-11-10
 
-	* Fixes a typo in revdep-pax script and documentation
-	* Make both PT_PAX and xattr PAX optionally enabled/disabled in
+	* fix a typo in revdep-pax script and documentation
+	* make both PT_PAX and xattr PAX optionally enabled/disabled in
 	configure.ac and propagated to src/paxctl-ng.c and script/paxmodule.c
+	* add -L -l which limits markings to only PT_PAX or XT_PAX when
+	both are possible
+	* add -d which deletes the XT_PAX xattr field
+	* silently ignore non-applicable command line flags so there is
+	more flexibility in scripting
+	* add proper exit code handling
 
 2012-07-29
 


             reply	other threads:[~2012-11-10 23:38 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-10 23:38 Anthony G. Basile [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-24  3:18 [gentoo-commits] proj/elfix:master commit in: / Sam James
2023-01-10  5:21 Sam James
2016-04-02 22:11 Anthony G. Basile
2016-02-28 21:14 Anthony G. Basile
2016-02-28 21:02 Anthony G. Basile
2016-02-28 17:15 Anthony G. Basile
2016-02-28 17:04 Anthony G. Basile
2016-02-28 16:28 Anthony G. Basile
2016-02-28 14:13 Anthony G. Basile
2016-02-28  7:12 Anthony G. Basile
2016-02-28  7:10 Anthony G. Basile
2016-02-13 21:29 Anthony G. Basile
2015-10-27 19:48 Anthony G. Basile
2015-10-24 18:32 Anthony G. Basile
2014-11-03 12:23 Anthony G. Basile
2014-10-13 22:19 Anthony G. Basile
2014-08-19 14:01 Anthony G. Basile
2014-07-30 16:32 ` Anthony G. Basile
2014-08-19 14:01 Anthony G. Basile
2014-07-30 16:40 ` Anthony G. Basile
2014-07-30 22:36 Anthony G. Basile
2014-08-19 14:01 ` Anthony G. Basile
2014-07-30 19:39 Anthony G. Basile
2014-08-19 14:01 ` Anthony G. Basile
2014-07-30 16:20 Anthony G. Basile
2014-07-21 21:05 Anthony G. Basile
2014-06-07 14:20 Anthony G. Basile
2014-06-07 14:18 Anthony G. Basile
2013-11-07 14:51 Anthony G. Basile
2013-05-21  2:21 Anthony G. Basile
2012-12-29  2:36 Anthony G. Basile
2012-12-29  1:36 Anthony G. Basile
2012-12-27  3:16 Anthony G. Basile
2012-12-16 21:31 Anthony G. Basile
2012-12-12 18:47 Anthony G. Basile
2012-11-10 22:26 Anthony G. Basile
2012-11-10 21:02 Anthony G. Basile
2012-11-10 21:01 Anthony G. Basile
2012-07-29 15:18 Anthony G. Basile
2012-07-28 12:46 Anthony G. Basile
2012-07-27 22:37 Anthony G. Basile
2012-07-24 12:53 Anthony G. Basile
2012-07-24 12:38 Anthony G. Basile
2012-07-21 19:04 Anthony G. Basile
2012-07-20 15:20 Anthony G. Basile
2011-12-29  0:53 Anthony G. Basile
2011-12-04 22:00 Anthony G. Basile
2011-12-04 21:47 Anthony G. Basile
2011-11-27  1:33 Anthony G. Basile
2011-11-27  1:12 Anthony G. Basile
2011-11-26 22:54 Anthony G. Basile
2011-11-15 19:37 Anthony G. Basile
2011-11-03 19:00 Anthony G. Basile
2011-11-02  9:30 Anthony G. Basile
2011-10-23 15:44 Anthony G. Basile
2011-10-23 14:57 Anthony G. Basile
2011-10-17 21:24 Anthony G. Basile
2011-10-12 10:53 Anthony G. Basile
2011-10-08 19:31 Anthony G. Basile
2011-09-18 23:06 Anthony G. Basile
2011-05-05 19:46 Anthony G. Basile
2011-05-04  2:24 Anthony G. Basile

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=1352590673.83520307969cc118b41f155bed6caebbea87ee6f.blueness@gentoo \
    --to=blueness@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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