From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/dev/ulm:master commit in: dev-tex/vc/, dev-tex/vc/files/
Date: Thu, 5 Nov 2015 17:25:53 +0000 (UTC) [thread overview]
Message-ID: <1446744329.e51e1cf12d0e8212881069ff8601d8f427efa190.ulm@gentoo> (raw)
commit: e51e1cf12d0e8212881069ff8601d8f427efa190
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Thu Nov 5 17:25:29 2015 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Thu Nov 5 17:25:29 2015 +0000
URL: https://gitweb.gentoo.org/repo/dev/ulm.git/commit/?id=e51e1cf1
dev-tex/vc: Fix parsing of git status output.
Package-Manager: portage-2.2.23
dev-tex/vc/ChangeLog | 6 ++++++
dev-tex/vc/files/vc-0.5-git-status.patch | 23 +++++++++++++++++++++++
dev-tex/vc/{vc-0.5.ebuild => vc-0.5-r1.ebuild} | 3 ++-
3 files changed, 31 insertions(+), 1 deletion(-)
diff --git a/dev-tex/vc/ChangeLog b/dev-tex/vc/ChangeLog
index 954383a..6c25e10 100644
--- a/dev-tex/vc/ChangeLog
+++ b/dev-tex/vc/ChangeLog
@@ -2,6 +2,12 @@
# Copyright 1999-2015 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
+*vc-0.5-r1 (05 Nov 2015)
+
+ 05 Nov 2015; Ulrich Müller <ulm@gentoo.org> -vc-0.5.ebuild,
+ +vc-0.5-r1.ebuild, +files/vc-0.5-git-status.patch:
+ Fix parsing of git status output.
+
15 May 2015; Ulrich Müller <ulm@gentoo.org> vc-0.5.ebuild,
+files/vc-0.5-fix-git-date.patch:
Fix date information in git.
diff --git a/dev-tex/vc/files/vc-0.5-git-status.patch b/dev-tex/vc/files/vc-0.5-git-status.patch
new file mode 100644
index 0000000..e67007d
--- /dev/null
+++ b/dev-tex/vc/files/vc-0.5-git-status.patch
@@ -0,0 +1,23 @@
+--- vc-orig/git-unix/vc
++++ vc/git-unix/vc
+@@ -20,5 +20,5 @@
+ git --no-pager log -1 HEAD --pretty=format:"Hash: %H%nAbr. Hash: %h%nParent Hashes: %P%nAbr. Parent Hashes: %p%nAuthor Name: %an%nAuthor Email: %ae%nAuthor Date: %ai%nCommitter Name: %cn%nCommitter Email: %ce%nCommitter Date: %ci%n" |gawk -v script=log -v full=$full -f vc-git.awk > vc.tex
+ if [ "$mod" = 1 ]
+ then
+- git status |gawk -v script=status -f vc-git.awk >> vc.tex
++ git status --porcelain |gawk -v script=status -f vc-git.awk >> vc.tex
+ fi
+--- vc-orig/git-unix/vc-git.awk
++++ vc/git-unix/vc-git.awk
+@@ -26,9 +26,9 @@
+
+ ### Process output of "git status".
+ ### Changed index?
+-script=="status" && /^# Changes to be committed:/ { modified = 1 }
++script=="status" && /^[MADRC]/ { if (modified == 0) modified = 1 }
+ ### Unstaged modifications?
+-script=="status" && /^# Changed but not updated:/ { modified = 2 }
++script=="status" && /^.[MD]/ { modified = 2 }
+
+
+
diff --git a/dev-tex/vc/vc-0.5.ebuild b/dev-tex/vc/vc-0.5-r1.ebuild
similarity index 92%
rename from dev-tex/vc/vc-0.5.ebuild
rename to dev-tex/vc/vc-0.5-r1.ebuild
index 278d9c9..88adcda 100644
--- a/dev-tex/vc/vc-0.5.ebuild
+++ b/dev-tex/vc/vc-0.5-r1.ebuild
@@ -1,6 +1,6 @@
# Copyright 1999-2015 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: $
+# $Id$
EAPI=5
@@ -20,6 +20,7 @@ S="${WORKDIR}/${PN}"
src_prepare() {
epatch "${FILESDIR}"/${P}-fix-git-date.patch
+ epatch "${FILESDIR}"/${P}-git-status.patch
}
src_compile() { :; }
reply other threads:[~2015-11-05 17:26 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=1446744329.e51e1cf12d0e8212881069ff8601d8f427efa190.ulm@gentoo \
--to=ulm@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