public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Daniel Pielmeier (billie)" <billie@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-libs/libisoburn: metadata.xml ChangeLog
Date: Thu, 21 Jan 2010 18:17:27 +0000	[thread overview]
Message-ID: <E1NY1ax-00035r-K2@stork.gentoo.org> (raw)

billie      10/01/21 18:17:27

  Modified:             metadata.xml ChangeLog
  Log:
  Add myself to maintainers.
  (Portage version: 2.1.6.13/cvs/Linux i686)

Revision  Changes    Path
1.4                  dev-libs/libisoburn/metadata.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/libisoburn/metadata.xml?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/libisoburn/metadata.xml?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/libisoburn/metadata.xml?r1=1.3&r2=1.4

Index: metadata.xml
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-libs/libisoburn/metadata.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- metadata.xml	9 Dec 2009 19:37:53 -0000	1.3
+++ metadata.xml	21 Jan 2010 18:17:27 -0000	1.4
@@ -2,6 +2,10 @@
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
 <herd>media-optical</herd>
+<maintainer>
+<email>billie@gentoo.org</email>
+<name>Daniel Pielmeier</name>
+</maintainer>
 <use>
 <flag name='external-filters'>Allow the use of external processes as file content 
 filters (Note: this is a potential security risk)</flag>



1.33                 dev-libs/libisoburn/ChangeLog

file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/libisoburn/ChangeLog?rev=1.33&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/libisoburn/ChangeLog?rev=1.33&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/libisoburn/ChangeLog?r1=1.32&r2=1.33

Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-libs/libisoburn/ChangeLog,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- ChangeLog	20 Jan 2010 18:01:56 -0000	1.32
+++ ChangeLog	21 Jan 2010 18:17:27 -0000	1.33
@@ -1,6 +1,9 @@
 # ChangeLog for dev-libs/libisoburn
 # Copyright 1999-2010 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-libs/libisoburn/ChangeLog,v 1.32 2010/01/20 18:01:56 billie Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-libs/libisoburn/ChangeLog,v 1.33 2010/01/21 18:17:27 billie Exp $
+
+  21 Jan 2010; Daniel Pielmeier <billie@gentoo.org> metadata.xml:
+  Add myself to maintainers.
 
   20 Jan 2010; Daniel Pielmeier <billie@gentoo.org>
   -libisoburn-0.4.2_p02.ebuild, -libisoburn-0.4.4_p00.ebuild:






             reply	other threads:[~2010-01-21 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 18:17 Daniel Pielmeier (billie) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-09 19:37 [gentoo-commits] gentoo-x86 commit in dev-libs/libisoburn: metadata.xml ChangeLog Daniel Pielmeier (billie)

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=E1NY1ax-00035r-K2@stork.gentoo.org \
    --to=billie@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