public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jeremy Olexa (darkside)" <darkside@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in app-shells/bash-completion: metadata.xml ChangeLog
Date: Wed, 11 Feb 2009 19:07:44 +0000	[thread overview]
Message-ID: <E1LXKQy-0002LB-IG@stork.gentoo.org> (raw)

darkside    09/02/11 19:07:44

  Modified:             metadata.xml ChangeLog
  Log:
  add myself to metadata
  (Portage version: 2.2_rc23/cvs/Linux x86_64)

Revision  Changes    Path
1.7                  app-shells/bash-completion/metadata.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-shells/bash-completion/metadata.xml?rev=1.7&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-shells/bash-completion/metadata.xml?rev=1.7&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-shells/bash-completion/metadata.xml?r1=1.6&r2=1.7

Index: metadata.xml
===================================================================
RCS file: /var/cvsroot/gentoo-x86/app-shells/bash-completion/metadata.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- metadata.xml	31 May 2007 03:32:50 -0000	1.6
+++ metadata.xml	11 Feb 2009 19:07:44 -0000	1.7
@@ -2,6 +2,7 @@
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
 <herd>shell-tools</herd>
+<maintainer><email>darkside@gentoo.org</email></maintainer>
 <longdescription>
   Since v2.04, bash has allowed you to intelligently program and extend its
   standard completion behavior to achieve complex command lines with just a



1.150                app-shells/bash-completion/ChangeLog

file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-shells/bash-completion/ChangeLog?rev=1.150&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-shells/bash-completion/ChangeLog?rev=1.150&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-shells/bash-completion/ChangeLog?r1=1.149&r2=1.150

Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/app-shells/bash-completion/ChangeLog,v
retrieving revision 1.149
retrieving revision 1.150
diff -u -r1.149 -r1.150
--- ChangeLog	8 Feb 2009 22:30:00 -0000	1.149
+++ ChangeLog	11 Feb 2009 19:07:44 -0000	1.150
@@ -1,6 +1,9 @@
 # ChangeLog for app-shells/bash-completion
 # Copyright 2002-2009 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/app-shells/bash-completion/ChangeLog,v 1.149 2009/02/08 22:30:00 josejx Exp $
+# $Header: /var/cvsroot/gentoo-x86/app-shells/bash-completion/ChangeLog,v 1.150 2009/02/11 19:07:44 darkside Exp $
+
+  11 Feb 2009; Jeremy Olexa <darkside@gentoo.org> metadata.xml:
+  add myself to metadata
 
   08 Feb 2009; Joseph Jezak <josejx@gentoo.org>
   bash-completion-20060301.ebuild:






             reply	other threads:[~2009-02-11 19:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 19:07 Jeremy Olexa (darkside) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-27  5:56 [gentoo-commits] gentoo-x86 commit in app-shells/bash-completion: metadata.xml ChangeLog Jeremy Olexa (darkside)

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=E1LXKQy-0002LB-IG@stork.gentoo.org \
    --to=darkside@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