public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Pacho Ramos (pacho)" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in app-shells/zsh: metadata.xml ChangeLog
Date: Mon, 23 Dec 2013 15:38:18 +0000 (UTC)	[thread overview]
Message-ID: <20131223153819.0E3172004C@flycatcher.gentoo.org> (raw)

pacho       13/12/23 15:38:18

  Modified:             metadata.xml ChangeLog
  Log:
  Prefer man-db as man provider (#467458)
  
  (Portage version: 2.2.7/cvs/Linux x86_64, signed Manifest commit with key A188FBD4)

Revision  Changes    Path
1.6                  app-shells/zsh/metadata.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-shells/zsh/metadata.xml?rev=1.6&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-shells/zsh/metadata.xml?rev=1.6&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-shells/zsh/metadata.xml?r1=1.5&r2=1.6

Index: metadata.xml
===================================================================
RCS file: /var/cvsroot/gentoo-x86/app-shells/zsh/metadata.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- metadata.xml	27 Aug 2013 06:27:45 -0000	1.5
+++ metadata.xml	23 Dec 2013 15:38:18 -0000	1.6
@@ -5,11 +5,6 @@
   <email>radhermit@gentoo.org</email>
   <name>Tim Harder</name>
 </maintainer>
-<maintainer>
-  <email>tove@gentoo.org</email>
-  <name>Torsten Veller</name>
-  <description>Interim maintainer</description>
-</maintainer>
 <longdescription>
   Zsh is a shell designed for interactive use, although it is also a
   powerful scripting language. Many of the useful features of bash, ksh,



1.230                app-shells/zsh/ChangeLog

file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-shells/zsh/ChangeLog?rev=1.230&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-shells/zsh/ChangeLog?rev=1.230&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-shells/zsh/ChangeLog?r1=1.229&r2=1.230

Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/app-shells/zsh/ChangeLog,v
retrieving revision 1.229
retrieving revision 1.230
diff -u -r1.229 -r1.230
--- ChangeLog	23 Dec 2013 06:09:32 -0000	1.229
+++ ChangeLog	23 Dec 2013 15:38:18 -0000	1.230
@@ -1,6 +1,9 @@
 # ChangeLog for app-shells/zsh
 # Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/app-shells/zsh/ChangeLog,v 1.229 2013/12/23 06:09:32 radhermit Exp $
+# $Header: /var/cvsroot/gentoo-x86/app-shells/zsh/ChangeLog,v 1.230 2013/12/23 15:38:18 pacho Exp $
+
+  23 Dec 2013; Pacho Ramos <pacho@gentoo.org> metadata.xml:
+  Prefer man-db as man provider (#467458)
 
 *zsh-5.0.4 (23 Dec 2013)
 





             reply	other threads:[~2013-12-23 15:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23 15:38 Pacho Ramos (pacho) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-08-27  6:27 [gentoo-commits] gentoo-x86 commit in app-shells/zsh: metadata.xml ChangeLog Tim Harder (radhermit)
2010-09-28  6:51 Tim Harder (radhermit)

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=20131223153819.0E3172004C@flycatcher.gentoo.org \
    --to=pacho@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